-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
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
M
and m
are normalized to ident m
#821
Comments
Oof. Yeah, there's a reason this is issue 1! oxidecomputer/typify#1 What could would you ideally like to see generated? |
I think I'd want to see something like a configurable prefix for disambiguation, or some structural suffix mapping i.e. In a perfect world the upstream would amend the spec, for the particular vendor, that won't happen unfortunately 😕 |
Thinking about this some more: What I really want, is a closure ( |
Setting aside the mechanism: what code would you like to see generated in this case? |
Given that depending on the context, any suffix will risk a collision, that was what motivated the user defined closure for normalization (with a sane default). |
An externally provided
openapi
spec file defineswhich generates
which won't compile. The root here is the normalization of the identifiers to be lowercase.
The text was updated successfully, but these errors were encountered: