Jeremy Whitlock

That sucks. It would had been cool to make sway better instead of ending up with a competitor but such is life. Let me know if I can help.

That would be great. You've been a great help with the Swagger tooling I've written and I'd rather us work together. So if I can help, let me know. Also,...

There is nothing to report yet. I've been on vacation and I haven't worked on anything in a few weeks. I'm back and I hope to get to this soon.

While the Swagger Specification is not very clear on things, there are a lot of details in https://github.com/apigee-127/swagger-tools/issues/241 that help explain how this should work. I think the reason this...

Yeah, we're into the realm of the OpenAPI Specification now. As for the context that matters to swagger-tools/sway, it's purely from a validation perspective.

We definitely plan on supporting it but I'm not 100% sure how to do it yet. In `swagger-tools`, a lot of heft and complexity comes from having a single library...

We're wrapping up the next sway release, bug/security fixes and enhancements. After that, 3.0 support will be our top priority. Sorry for the delay.

I don’t see why threatening to fork is required when a PR, or PRs, would suffice. I’ve been the only active developer in this project from day one and like...

Well, let's make this happen. I'm putting in the time now and I'd love some help. My plan is to release `2.0.0` by EOW _(barring any unexpected conflict)_ and then...

Now that `[email protected]` is released, `OASv3.x` support is the next major feature being worked on for `sway`.