Open janishorsts opened 1 month ago
I'd rewrite
D int `oas:"d,body,json"`
I.e. [name][where][options]
I don't want to enforce the sequence, it makes it harder to use. The setting names do not conflict, they can be used in any order.
If you rename the tag to "OpenAPI Request Specification" you can use this for logo: 🚣 ;)
In principle, the syntax is <name>,<settings>
where <settings>
is a comma-separated list of settings.
Currently, the field tag has multiple names that increase the risk of conflicts with other field tags from other packages. Breaking change.
Currently
Next
Use single field tag "oas" (OpenAPI Specification). All settings are comma-separated as before. Additionally, a new origin setting is added: