fix(generator): add serde rename in case of rust keyword conflict#94
Merged
lerouxrgd merged 3 commits intolerouxrgd:masterfrom Mar 7, 2026
Merged
fix(generator): add serde rename in case of rust keyword conflict#94lerouxrgd merged 3 commits intolerouxrgd:masterfrom
lerouxrgd merged 3 commits intolerouxrgd:masterfrom
Conversation
Owner
|
Thanks for the fix ! |
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.
This patch fixes serde rename attribute not being properly added when field names conflict with Rust keywords but have different casing (e.g., "Type" vs "type").
When an Avro field name like Type (capital T) conflicts with a Rust keyword (type), the code generator renames it to r#type for the Rust field name, but fails to add the #[serde(rename = "Type")] attribute because the existing logic didnt handle this case correctly