We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rust-axum
Generated response naming schemes for rust-axum is really bad:
pub enum DeleteOrderResponse { /// Invalid ID supplied Status400_InvalidIDSupplied, /// Order not found Status404_OrderNotFound, }
This breaks Rust's naming conventions (PascalCase) and will trigger an endless amount of Clippy warnings (that I don't want to just ignore).
PascalCase
I think a better naming scheme would be:
pub enum DeleteOrderResponse { /// Invalid ID supplied Status400InvalidIDSupplied, /// Order not found Status404OrderNotFound, }
Or more true to Rust's conventions:
pub enum DeleteOrderResponse { /// Invalid ID supplied InvalidIDSupplied, /// Order not found OrderNotFound, }
This can potentially generate duplicate names, but the compiler can catch the error just fine so it's not a real issue.
I tried to change the naming scheme in the configuration, but couldn't figure out how.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Is your feature request related to a problem? Please describe.
Generated response naming schemes for
rust-axum
is really bad:This breaks Rust's naming conventions (
PascalCase
) and will trigger an endless amount of Clippy warnings (that I don't want to just ignore).Describe the solution you'd like
I think a better naming scheme would be:
Or more true to Rust's conventions:
This can potentially generate duplicate names, but the compiler can catch the error just fine so it's not a real issue.
Describe alternatives you've considered
I tried to change the naming scheme in the configuration, but couldn't figure out how.
The text was updated successfully, but these errors were encountered: