#44 Add support for baseURI #45
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a new prop called bathPath which defaults to the current directory the app launches from initially, or respecting the
<base href="..." />tag's value (both of which document.baseURI resolve to if set / not set). This PR then uses this to lob off the 1st part of the detected pathname to ensure that the baseURI is not required in the routes defined. This allows for links to be relative (<a href="whatever-route">) or full reference (<a href="https://domainname/path/here/yet-route-is-set-here">or<a href="/path/here/whatever-route">)