-
-
Notifications
You must be signed in to change notification settings - Fork 389
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
fix(loader): fix publicPath regression #384
Conversation
... when the publicPath is set to an empty string. The publicPath should resolve to an empty string in this case and _not_ `/`
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.
Looks good, please add tests
Ignore CI problem , just add tests and we can release new version |
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.
Good job, let's wait CI green
Also please change email on commit and do force push, need accept CLA, thanks |
@evilebottnawi year, sorry about that. I think it is fixed now. |
Codecov Report
@@ Coverage Diff @@
## master #384 +/- ##
=======================================
Coverage 65.19% 65.19%
=======================================
Files 4 4
Lines 408 408
Branches 84 84
=======================================
Hits 266 266
Misses 118 118
Partials 24 24
Continue to review full report at Codecov.
|
... when the publicPath is set to an empty string. The publicPath should resolve to an empty string in this case and not
/
.This PR contains a:
Motivation / Use-Case
A regression caused by #373 makes it impossible to set
publicPath
to an empty string. This fix brings this feature back.Breaking Changes
Additional Info