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.
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
feat: set dynamic base when rendering page #9220
feat: set dynamic base when rendering page #9220
Changes from 21 commits
f0834b9
160084a
12c2787
26f919a
be5a74f
dff5768
6250f2b
97d5728
6aaf6e6
e53011e
9511492
ebb0a68
92197dd
81fe6c6
039b681
7e853ee
23ac8e9
8ceade0
2dd7150
8aedd0d
0779dd1
5985657
7892386
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why split.at(-1)? What if the base path spans more than one
/
, like/foo/bar
? We know the base has to start with a slash, so why notThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Consider a basepath like
/a/b/c
. If you're rendering that route, then{base}/d
should resolve to/a/b/c/d
.With non-relative paths, that's easy — just use
base
as written. But if you're using a relative path, then it needs to be./c
to produce./c/d
to resolve to/a/b/c/d
(or../b/c/d
, or../../a/b/c/d
, but there's no point in doing that).With your suggestion, it would be
./a/b/c
, which would resolve to/a/b/a/b/c/d