-
Notifications
You must be signed in to change notification settings - Fork 18
Conversation
@adambutler Thanks! We'll take a look at this soon. |
👋 Just pinging a reminder on this PR. I just wanted to mention I've been using this for https://github.com/Nexmo/nexmo-developer without any issues so far. You can see an example where this is used here |
I apologize for not getting around to this yet. Unfortunately, our internal usage of OpenAPI is not yet on v3, so this may be challenging to merge at this time. I'll have more time to look in-depth at this in the next few weeks. |
For the time being, I think we're going to have to avoid merging this. We rely on v2 of the specification internally and this would break our usage. I'll come back to this PR if / when we upgrade. Sorry for the delay in the response! |
Hey @drewolson thanks for following up on this but I'd like to make a case for you reconsidering if possible. I appreciate that you using v2 of the spec but I think when you take the namespace of something encompassing like
I've changed the version of this following Semver to gem 'open_api_parser', '~> 1.2.1' Alternatively I'd like to ask if you would be willing to do any of the following:
If none of these are options for you I'll likely fork the project into a seperate Gem and would welcome contirbutions if / when you've migrated to OAS3. |
@adambutler perhaps you can release a V3 yourself by forking this project? |
@why-el I ended up building this project: https://github.com/nexmo/oas_parser |
Oh yeah, I was actually looking at that right now. 👍 |
Changes library to support for Open API Specification v3.0.0
Fixes #5