Repository navigation
Add support for --name-mappings #71
Description
We have a 3rd party spec that contains similar names in schema. Can name mappings be added to the library? Or is there already a way to use name mappings?
Schema sample:
"properties": {
"feature_enabled": {
"type": "boolean",
"description": "Whether the feature is enabled or not.",
"example": true
},
"featureEnabled": {
"deprecated": true,
"type": "boolean",
"description": "Use `feature_enabled` instead.",
"example": true
}
...
}
Result:
public static final String JSON_PROPERTY_FEATURE_ENABLED = "feature_enabled";
@javax.annotation.Nullable
private Boolean featureEnabled;
public static final String JSON_PROPERTY_FEATURE_ENABLED = "featureEnabled";
@javax.annotation.Nullable
private Boolean featureEnabled;
The issue is that the same constant name is generated.
Activity
wing328 commentedon Nov 3, 2025
thanks for the suggestions
definitely sounds good
I wonder if you've time to contribute the enhancement.
MoonWalkerAZ commentedon Nov 3, 2025
Hi, yes. I can prepare a PR for this?
wing328 commentedon Nov 3, 2025
yes please fork the repo and file a PR with the suggested change.
MoonWalkerAZ commentedon Nov 3, 2025
Done:
#72
bu3 commentedon Nov 17, 2025
Closing the issue since the PR was merged. Thanks @MoonWalkerAZ for your contribution