thegagne
thegagne
It would be great to have an example that works with flask.
It would be fantastic if Hono + Zod Openapi would support Problem Details (RFC 9457). This could include registered Problem Types (https://www.iana.org/assignments/http-problem-types/http-problem-types.xhtml), or support custom ones. Something like ``` import...
Fixes #358 . URL only fields should be named `url` not `uri`. ## 🍱 Types of changes What types of changes does your code introduce to AEP? _Put an `x`...
Recently running the OAS linter on a project, it got flagged for fields containing `url` in the field names. Current guidance field names is that they should be `uri` and...
The tooling page could use some design improvements. Some suggestions: - While the graphic is helpful to understand how things fit, it's not really the way people want to first...
**Empty Fields** For fields that are empty, should they be omitted, empty stringed, or nulled? ``` GET /publishers/{publisher_id}/books? { "results": [{ ... }], "next_page_token": "", -> empty string, null, or...
While reading AEP-4, I noticed that the Guidance and Examples sections describe general resource type naming and annotation rules, but they don’t seem directly relevant to OpenAPI (OAS) specifically. Later...