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 OR in Journey patterns #17827

Merged
merged 1 commit into from
Dec 1, 2014
Merged

Fix OR in Journey patterns #17827

merged 1 commit into from
Dec 1, 2014

Conversation

rkh
Copy link
Contributor

@rkh rkh commented Nov 29, 2014

Journey supported OR tokens right from the start (using the pipe character), they are translated into proper AST nodes. However, the rule for translating them into a regular expression was missing, so I added it.

I don't understand the router well enough (yet) to check if that's all that's needed to make them generally work. The code I actually started looking at, was the code for generating URLs, not sure if that works properly with OR literals in there. @tenderlove informed me, that he has some refactoring of said code pending, so I refrained from diving into it.

My main motivation for looking into this in the first place, was a conversation I had with @amatsuda about doing a spike on using Mustermann in Rails to see if it would speed up url_helpers (it's really fast at expanding a URL pattern into a full URL).

tenderlove added a commit that referenced this pull request Dec 1, 2014
@tenderlove tenderlove merged commit c9a5ed2 into rails:master Dec 1, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants