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

API routes should take precedent over static routes when not using an API prefix #18

Open
arobson opened this issue Nov 26, 2014 · 0 comments
Open

API routes should take precedent over static routes when not using an API prefix #18

arobson opened this issue Nov 26, 2014 · 0 comments
Assignees
@arobson
Labels
bug

Comments

@arobson
Copy link
Contributor

arobson commented Nov 26, 2014

By default, AH provides an API prefix for all resource routes to prevent collision issues. When using an empty API prefix (effectively hosting static resources and API calls at the same base URL), AH should register paths with express to avoid collisions.
@arobson arobson added the bug label Nov 26, 2014
@arobson arobson self-assigned this Nov 26, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@arobson arobson

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@arobson