-
Notifications
You must be signed in to change notification settings - Fork 462
feat: Make NetworkMetricsPipelineStage public #3853
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: develop-2.0.0
Are you sure you want to change the base?
Conversation
| /// </summary> | ||
| [BurstCompile] | ||
| internal unsafe struct NetworkMetricsPipelineStage : INetworkPipelineStage | ||
| public unsafe struct NetworkMetricsPipelineStage : INetworkPipelineStage |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe that due to this change you should bump package version in package.json to 2.9.0. But vetting test should verify this (will fail if you should bump it)
michalChrobot
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good to me but @NoelStephensUnity @EmandM please double check me
@simon-lemay-unity I would aim to merge this before Friday since we have a release next week
Purpose of this PR
As the title says, this PR makes
NetworkMetricsPipelineStagepublic. This is required if you want to use custom drivers that are compatible with the multiplayer tools package as you need to register that pipeline stage before it can be used to create pipelines.Jira ticket
N/A
Changelog
NetworkMetricsPipelineStagefor Unity Transport is now part of the public API. This allows using it in custom implementations ofINetworkStreamDriverConstructorthat want to maintain compatibility with the multiplayer tools package.NullReferenceExceptioninUnityTransportwhen using a customINetworkStreamDriverConstructorthat doesn't use all the default pipelines and the multiplayer tools package is installed.Documentation
Testing & QA (How your changes can be verified during release Playtest)
Functional Testing
Manual testing :
Manual testing doneAutomated tests:
Covered by existing automated testsCovered by new automated testsDoes the change require QA team to:
Review automated tests?Execute manual tests?Provide feedback about the PR?Backports
N/A