remove reverend in favor of path-to-regexp.compile #2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
8 tasks
|
Tests failed due to existing issue. |
|
@jasisk thanks for the PR |
indieisaconcept
added a commit
that referenced
this pull request
May 13, 2015
remove reverend in favor of path-to-regexp.compile
|
My pleasure. 😀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Path-to-regexp, which powers Reverend, has recently added the ability to reverse routes, rendering
Reverendunnecessary. As such,Reverendis in the process of being deprecated.The sole differences between the implementation in
Reverendand that ofpath-to-regexpis a bit of duck-typing to prevent throws. This small amount of duck-typing can be seen in the shim branch.