We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Flavour currently uses hash-based routing, which works great for many cases. For a path like "/buttons", the URL looks like:
https://frequal.com/tea-sampler/#/buttons
However, it would be great to have an option to use path-based routing. For the same "/buttons" path, a path-based URL would look like this:
https://frequal.com/tea-sampler/buttons
For some Flavour apps path-based routing is preferred for these reasons:
For developers, path-based routing should be easy to enable. Ideally it would be as easy as:
Routing.usePathStrategy();
For direct URLs to work, there may be a need to set the base URL in index.html:
<base href="https://frequal.com/tea-sampler/" />
web.xml will also need to redirect to index.html:
<error-page> <location>/index.html</location> </error-page>
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Flavour currently uses hash-based routing, which works great for many cases. For a path like "/buttons", the URL looks like:
https://frequal.com/tea-sampler/#/buttons
However, it would be great to have an option to use path-based routing. For the same "/buttons" path, a path-based URL would look like this:
https://frequal.com/tea-sampler/buttons
For some Flavour apps path-based routing is preferred for these reasons:
For developers, path-based routing should be easy to enable. Ideally it would be as easy as:
Routing.usePathStrategy();
For direct URLs to work, there may be a need to set the base URL in index.html:
<base href="https://frequal.com/tea-sampler/" />
web.xml will also need to redirect to index.html:
<error-page> <location>/index.html</location> </error-page>
The text was updated successfully, but these errors were encountered: