-
Notifications
You must be signed in to change notification settings - Fork 65
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
Allow regular expressions to be used for route. #157
Conversation
|
Codecov Report
@@ Coverage Diff @@
## master #157 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 1 1
Lines 80 81 +1
=========================================
+ Hits 80 81 +1
Continue to review full report at Codecov.
|
hi. any feedback on this would be appreciated. if it hasn't been looked at for a reason, perhaps I can resolve any grievances to move it forward? |
My apology! There is no grievances or anything. I totally forgot about the PR. If Regex is to supported in |
No worries.
Makes sense. I'll make the modifications at some point in the next few days. Thanks. |
updated. I'm open to any simplifications you can think of that might apply. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just some refactor I think that would make it clearer.
* instead excluding types, now including the expected type in the execution path. Co-authored-by: Hoang <[email protected]>
* instead excluding types, now including the expected type in the execution path. Co-authored-by: Hoang <[email protected]>
Awesome! LGTM |
Released in |
Closes #156