fix(rust): apply consistent pascalcase naming for nested types#3548
Merged
chaokunyang merged 1 commit intoapache:mainfrom Apr 12, 2026
Merged
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
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.
Why?
Rust generator was creating naming conflicts for nested types where module paths and struct names could collide and cause compilation errors.
What does this PR do?
Applies consistent PascalCase naming to type names when resolving nested type references and building struct definitions. Added tests for nested type scenarios.
Related issues
Fixes #3547
AI Contribution Checklist (if applicable)
N/A
Does this PR introduce any user-facing change?
Yes, code that previously failed to compile due to naming conflicts will now generate valid Rust code.
Benchmark (if perf-related)
N/A