Fix for indexing nodes by id with string based ids #191
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
|
|
|
Did you verify it works as expected? I added your changes but I don't see the IRDIs showing up. |
|
Found another bug. It has been fixed here: https://github.com/OPCF-Members/UA-ModelCompiler |
Yes, I both see changes in the generated initialization strings in *.Classes.cs as well as the actual HasDictionaryEntry references in a client.
Thank you! |
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.
When compiling the Padim node set, the IRDI dictionary references are missing in the generated C# classes. This is because string based node ids are currently not considered by the
ModelDesignerValidator.