Set locationType to none in tests #2586
Merged
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.
Fixes #2559
none
Previously we were setting location to
auto
in test environment so that we get a<base>
tag during build (which testem needs), and then setting it back tonone
in thestartApp
helper before running the tests. But that last step was removed, which caused the tests to run with locationauto
, which breaks reloads.It might be a bit confusing to set
locationType:'auto'
inenvironment.js
just to get a<base>
tag, when actually the tests would run withlocationType: 'none'
. So I just set location tonone
and added a<base>
tag anyway.@rwjblue is it safe to set a
<base>
tag in locationnone
or was de7c6bc fixing a previous issue?