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

Fix route requirements bug #1788

Merged
merged 2 commits into from
Sep 6, 2018

Conversation

darren987469
Copy link
Contributor

@darren987469 darren987469 commented Sep 6, 2018

Fix spec in #1783

This was a bug introduced by commit 9f4ba67.

The commit replaces options[:route_options].clone.merge(...) with options[:route_options].clone.reverse_merge(...).
That causes disappear of the requirements in namespace.

@darren987469 darren987469 force-pushed the fix_route_requirements_bug branch from ee84cdc to b473fc0 Compare September 6, 2018 13:32
This was a bug introduced by commit 9f4ba67. The commit
replaces `options[:route_options].clone.merge(...)` with
`options[:route_options].clone.reverse_merge(...)`.
That causes disappear of the requirements in namespace.
@darren987469 darren987469 force-pushed the fix_route_requirements_bug branch from b473fc0 to c701d48 Compare September 6, 2018 13:53
@dblock dblock merged commit 41b7519 into ruby-grape:master Sep 6, 2018
@dblock
Copy link
Member

dblock commented Sep 6, 2018

Amazing, merged.

@darrellnash
Copy link

Thanks @darren987469! Looks great.

terrchen pushed a commit to terrchen/gitlab that referenced this pull request Jul 9, 2020
The issue is that the requirement: for the route was clobbering the
requirement: for the containing namespace. This was since fixed in
ruby-grape/grape#1788, and pulled in
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/33450.
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