-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
after specified API's serializers using format,the api.type requests are not found #914
Comments
By previous version you mean 0.9.0, right? This was introduced deliberately in #809. We've discussed undoing that, I would still merge a PR. |
I also meet this problem after upgrading Grape, #809 is a break change and big problem for me. Before upgrading, I specified the API format:
I can access API by api and api.format_type
or
After upgrading, /account/login.json will return 404 not found. If remove "format :json", only /account/login.json can be used.
But, out client use both /account/login and /account/login.json to access our API before. |
You should be able to restore the old behavior by ensuring you have more than one format "supported", so after |
The culprit is here. |
This has been reverted via #1001, please test. |
if i specified the API's serializers using format:
the api will return 404 not found when called using api.type,such as:
I found this issue in version 0.10.1 and it's ok in previous version
The text was updated successfully, but these errors were encountered: