Skip to content
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: fall back to default value when publicPath is falsy #4365

Merged
merged 5 commits into from Nov 20, 2018
Merged

Conversation

manniL
Copy link
Member

@manniL manniL commented Nov 19, 2018

Types of changes

  • Bug fix (a non-breaking change which fixes an issue)
  • New feature (a non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Description

Resolves #4364

Checklist:

  • My change requires a change to the documentation.
  • I have updated the documentation accordingly. (PR: #)
  • I have added tests to cover my changes (if not applicable, please state why)
  • All new and existing tests are passing.

@manniL manniL requested a review from pi0 November 19, 2018 23:22
@codecov-io
Copy link

codecov-io commented Nov 19, 2018

Codecov Report

Merging #4365 into dev will increase coverage by 0.01%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##              dev    #4365      +/-   ##
==========================================
+ Coverage   91.53%   91.55%   +0.01%     
==========================================
  Files          56       56              
  Lines        1891     1895       +4     
  Branches      476      477       +1     
==========================================
+ Hits         1731     1735       +4     
  Misses        150      150              
  Partials       10       10
Impacted Files Coverage Δ
packages/config/src/options.js 94.89% <100%> (+0.15%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 27e79be...4e51f3d. Read the comment docs.

@manniL
Copy link
Member Author

manniL commented Nov 19, 2018

Would suggest releasing a patch (details in the linked issue above) after merging.

pi0
pi0 previously approved these changes Nov 20, 2018
@pi0
Copy link
Member

pi0 commented Nov 20, 2018

@manniL I have an alternative way to fix this: We can force add a trailing slash to the publicPath. This not only resolves this bug but also auto-fixes the situations that user forgot to add it.

@manniL
Copy link
Member Author

manniL commented Nov 20, 2018

@pi0 I'd combine both solutions 👍

@manniL manniL requested review from pi0 and clarkdo November 20, 2018 14:14
@Atinux Atinux merged commit e0537d5 into dev Nov 20, 2018
@manniL manniL deleted the fix-public-path branch November 20, 2018 17:20
pi0 pushed a commit that referenced this pull request Nov 20, 2018
* test: let tests fail

* fix: add falsy default fallback

* fix(publicPath): force adding trailing slash

* fix: also change _publicPath
@lock
Copy link

lock bot commented Dec 20, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Dec 20, 2018
@danielroe danielroe added the 2.x label Jan 18, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Validating publicPath value in Nuxt Config [v2.3.1]
6 participants