Use correct relative path format for EFM redirects #2253
Merged
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
josh-heyer
added
the
deploy
|
Making this a hotfix to avoid disturbing develop |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What Changed?
This is almost certainly my fault. I used path.resolve() instead of URL path merging for these, which... Leads to situations where relative paths behave differently from what one would normally expect on the web.
Use ../ to walk up where necessary for EFM redirects. @drothery-edb I suspect you had most of these correct the first time...
Checklist
Please check all boxes that apply (
[ ]is unchecked,[x]is checked)Content