fix: avoid throwing exception when using NetworkList without a NetworkManager (#2539) #2540
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolve #2539
This PR add a check that m_NetworkBehaviour is not null before calling the
CanClientWrite
function.I did it exactly the same way it's already done for NetworkVariable.
With this PR, operations on the list are done and throws the anyoning warning (
NetworkVariable<T>
do the same)Changelog
NetworkList
throwing exception when used without a NetworkManager in scene. (Can't do operations onNetworkList
with noNetworkManager
(offline) #2539)Testing and Documentation