Skip to content
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

Set default parameter location based on consumes #927

Merged
merged 5 commits into from
May 10, 2024

Conversation

dhruvCW
Copy link
Contributor

@dhruvCW dhruvCW commented May 7, 2024

Just a fork of #880 that is based on the latest changes in master.

.rubocop.yml Outdated Show resolved Hide resolved
Copy link
Member

@LeFnord LeFnord left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks @dhruvCW
but I have one big question, ite seems now the consumes key must be given,
is ot what you want?
want to see a fallback, if it isn't defined then json should be consumed

@dhruvCW
Copy link
Contributor Author

dhruvCW commented May 9, 2024

thanks @dhruvCW … but I have one big question, ite seems now the consumes key must be given, is ot what you want? want to see a fallback, if it isn't defined then json should be consumed

Hey 👋

we use consumes from the method[:consumes] value this is by default set to application/json so I think that should be enough of a fallback. Or am I not understanding your concern 😅

@dhruvCW dhruvCW requested a review from LeFnord May 9, 2024 09:12
Copy link
Member

@LeFnord LeFnord left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah @dhruvCW it makes sense, thanks

@LeFnord LeFnord merged commit e7856de into ruby-grape:master May 10, 2024
21 checks passed
@dhruvCW dhruvCW deleted the params_based_on_consumes branch May 10, 2024 11:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants