TranslateBrowsePath fix. #1271
Merged
TranslateBrowsePath fix. #1271
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…enceTypeId is not specified.
mregen
approved these changes
Feb 2, 2021
fremat
pushed a commit
to fremat/UA-.NETStandard
that referenced
this pull request
Feb 10, 2021
…enceTypeId is not specified. (OPCFoundation#1271)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Minor server compliance fix for TranslateBrowsePathsToNodeIds.
According to specs, IncludeSubtypes should be ignored when ReferenceTypeId is not specified.
This fixes the case when a client sends
RelativePath.ReferenceTypeId = nullandIncludeSubtypes = falsein aTranslateBrowsePathrequest