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

Can't use regular expression routes: Cannot currently resolve a regular expression path #887

Closed
LeCoupa opened this issue Oct 5, 2014 · 5 comments
Assignees
Labels
Milestone

Comments

@LeCoupa
Copy link

LeCoupa commented Oct 5, 2014

When I'm trying to define one of my route's path with a regex, the chrome debugger says:

Exception in template helper: Error: Cannot currently resolve a regular expression path

That's strange. In previous version of Iron Router, this was possible?

@tmeasday
Copy link
Contributor

tmeasday commented Oct 6, 2014

Hi @LeCoupa - I'm not sure IR could ever resolve a regular expression -- just parameterize it. Are you calling Router.path() or the like for this path?

@tmeasday tmeasday added this to the Requires Triage milestone Oct 6, 2014
@LeCoupa
Copy link
Author

LeCoupa commented Oct 6, 2014

I managed to do it this way as it was finally a simple case:

Router.map ->
  @route 'JournalRoot',
    path: '/journal/:tag?'
    yieldTemplates: 'JournalPreview': { to: 'journalContent' }

The error was triggered as soon as I set path with a regex. Is this possibility planned for future versions of Iron Router?

@tmeasday
Copy link
Contributor

tmeasday commented Oct 6, 2014

Seems like a bug with the new version.

@tmeasday tmeasday modified the milestones: Next Release, Requires Triage Oct 6, 2014
@tmeasday tmeasday added the bug label Oct 6, 2014
@tmeasday tmeasday changed the title Error: Cannot currently resolve a regular expression path Can't use regular expression routes: Cannot currently resolve a regular expression path Oct 6, 2014
@cmather cmather added fixed and removed bug labels Oct 26, 2014
@cmather cmather closed this as completed Oct 26, 2014
@cmather
Copy link
Contributor

cmather commented Oct 26, 2014

Will go out in next pre.

@fvpDev
Copy link

fvpDev commented Jul 13, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants