Generate schema properties in the original order#1722
Generate schema properties in the original order#1722diamondburned wants to merge 1 commit intooapi-codegen:mainfrom
Conversation
This commit temporarily switches to a fork of kin-openapi that provides the original ordering of the Properties object. This provides a way for this tool to generate the properties in the original order as they were written in the YAML file.
|
#1388 will essentially replace this PR with a few simple tweaks -_- |
|
Property ordering is cosmetic, and it doesn't affect behavior, so it's better to stay on the official release of kin-openapi than to use someone else's fork. Why is it important to preserve property order in generated code that you won't be editing? |
Right. There's a PR for this to kin-openapi, which is why this PR is a draft. See getkin/kin-openapi#1003.
Because the Go types are used for documentation when writing Go code. It is what you see first when you Go to Definition, not an external OpenAPI documentation. |
2 participants
This commit temporarily switches to a fork of kin-openapi that provides
the original ordering of the Properties object. This provides a way for
this tool to generate the properties in the original order as they were
written in the YAML file.