[C#] fix: handle case when valueRef is with enum type prefix #1092
Conversation
This file contains hidden or 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
vyazelenko added a commit that referenced this pull request Nov 3, 2025
vyazelenko added a commit that referenced this pull request Nov 3, 2025
| @unsafePtr Thanks for the fix. It is available in 1.36.1 release. |
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
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.
Background
Tried to generate models from Binace Spot spec which got following line
<field id="1" name="filterType" type="filterType" presence="constant" valueRef="filterType.TrailingDelta"/>This is producing incorrect code for c# where whole valueRef is considered as constant. In contrast this case is handled in C++. or in Rust.