Mathew Polzin

@protestContest I am at least initially liking your idea. To me, it's nice if the options for "dash conversion" are fairly high level (i.e. operate on everything or operate on...

I'll call this issue closed by https://github.com/beam-community/jsonapi/pull/310 but if anyone wants to have it re-opened (or possibly even better open a new targeted ticket) because your needs aren't covered by...

I think I'll merge this soon and start working on release notes for a new release (there will have been a solid chunk of changes, not just this PR) if...

This is mostly completed (but not fully tested yet) by: https://github.com/mattpolzin/OpenAPIKit/pull/263

This isn't necessary to release v3.0.0, but I do still want to have this validation. This will get implemented similarly to other optional validations (it won't get added to the...

I'm not totally sure this is necessary; I think I'll leave this for after the 3.0.0 release, at least.

It would definitely be important for any tool that read in 3.0.x and operated against the `OpenAPIKit` module for some logic but then wanted to write back out 3.0.x. I...

Per the previous comment, this has started to be implemented by producing warnings during decoding that can then be turned into errors by validating the document (which defaults to a...

At some point I deleted the Jira OpenAPI compatibility suite test and I have since implemented the suggested warning for multiple status codes so I will close this issue in...

I suspect that macros could be very useful here. I haven’t been coding in Swift enough lately to have found the time to get up to speed on Swift Macros,...