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.

Sign up for GitHub

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

Jump to bottom

"Cascading" paths #2

Open
enygma opened this issue Jun 25, 2015 · 1 comment
Open

"Cascading" paths #2

enygma opened this issue Jun 25, 2015 · 1 comment

Comments

@enygma
Copy link
Member

enygma commented Jun 25, 2015

Currently Invoke only supports exact path matching. The concept of "cascading" paths should be introduced, allowing a developer to say "anything under /admin is protected" by just specifying one entry and a "cascade" option:

/foo/bar/admin
  protected: on
  cascade: on

This would not only protect /foo/bar/admin but also anything under them including things like /foo/bar/admin/file.txt and /foo/bar/admin/user/view/username.
@enygma
Copy link
Member Author

enygma commented Jul 26, 2015

One update on this, I'm of the opinion that, if it hits another match that more specifically matches the requested URI those settings should override not merge with the current ones. This would help to eliminate potential ambiguity in how the settings are being interpreted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@enygma