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

Add support for any() or all() convenience method #31

Closed
jeremydaly opened this Issue Apr 24, 2018 · 2 comments

Comments

Projects
None yet
1 participant
@jeremydaly
Copy link
Owner

jeremydaly commented Apr 24, 2018

Saw this in a few places and it could be used to solve some use cases. Devs would need to handle the METHOD on there own.

@jeremydaly jeremydaly added this to the v0.6 milestone May 2, 2018

@jeremydaly

This comment has been minimized.

Copy link
Owner

jeremydaly commented May 16, 2018

I'm going to stick to the ANY convention of API Gateway.

@jeremydaly

This comment has been minimized.

Copy link
Owner

jeremydaly commented May 16, 2018

The first part of this was straight forward. I added a new method called ANY directly to the routes structure. I had to change the priority of processing for HEAD aliasing so that wildcard routes (including ANY wildcards) process before default aliasing for HEAD requests. All the tests continue to pass, so I'm pretty sure this is the preferred behavior.

@jeremydaly jeremydaly closed this May 16, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment