-
Notifications
You must be signed in to change notification settings - Fork 473
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix handling of HTTP status codes from routes #669
Conversation
Damn, did this drive-by-change and forgot to adapt the specs... Will do so... |
After additional investigation it looks like there are multiple ways to define status codes and they result in different representations in the internal structures. The routes used for the specs in this gem use
whereas the Grape documentation (and our application) uses
which also ends up in the same structure. After checking the Grape README, I did not explicitly see |
the keys has changed, see: grape#describing-methods, so former the difference is, that please have in mind these keys would only be used by grape-swagger |
2 similar comments
Just a quick update: I haven't forgotten about this PR, just been a bit low on time for OSS work - I have a couple of free days coming up this week and will take care of getting all the different variations of this covered then. |
@milgner thanks for the update 😄 |
Oh no, looks like my changes tipped the metrics for |
* [#667](https://github.com/ruby-grape/grape-swagger/pull/667): Make route summary optional - [@obduk](https://github.com/obduk). Generated by 🚫 danger |
thanks @milgner … please can you rebase and update the CHANGELOG with your entry |
👍 Done! |
thanks again … |
After updating Grape, the documentation could not be generated anymore.
Upon investigation it turned out that the HTTP codes were not stored in a hash (anymore) but as a two-element array with the status code first and a message second. After applying this patch, documentation was generated successfully again.