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

Test out inheritance for writing custom route matching code #15

Open
rictic opened this issue Feb 17, 2016 · 4 comments
Open

Test out inheritance for writing custom route matching code #15

rictic opened this issue Feb 17, 2016 · 4 comments

Comments

@rictic
Copy link
Collaborator

rictic commented Feb 17, 2016

This won't land until the extends branch in Polymer is merged, but we should test it out to be confident that this should work.

@rictic rictic self-assigned this Feb 17, 2016
@rictic rictic added this to the public-release milestone Feb 17, 2016
@rictic rictic mentioned this issue Feb 17, 2016
@rictic rictic modified the milestones: v1.1, public-release Feb 17, 2016
@rictic
Copy link
Collaborator Author

rictic commented Mar 28, 2016

The test succeeded, now just waiting on inheritance to land in Polymer core.

@cdata cdata modified the milestones: v1.0.0 (Stable), v0.2.0 Mar 31, 2016
@arthurevans
Copy link
Contributor

Will this handle things like having one route handle:

  • /start/
  • /docs/
  • /tools/

but not:

  • /search/
  • /api/

... because I can't figure out how to do that now.

@rictic
Copy link
Collaborator Author

rictic commented Apr 27, 2016

@arthurevans You could definitely extend the route matching logic to support that use case.

@arthurevans
Copy link
Contributor

Cool. I don't suppose you have any ideas for how we could do this now...? Asking for a friend. Or a friendly website.

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

No branches or pull requests

3 participants