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

feat(basePath): use basePath for keys only #74

Merged
merged 1 commit into from
Aug 21, 2017

Conversation

mastilver
Copy link
Contributor

BREAKING CHANGE:

  • basePath is not ignored when publicPath is used
  • basepath is only modifying manifest keys

closes #69

BREAKING CHANGE:
- basePath is not ignored when publicPath is used
- basepath is only modifying manifest keys
@mastilver mastilver added this to the v2.x milestone Aug 21, 2017
@codecov-io
Copy link

codecov-io commented Aug 21, 2017

Codecov Report

Merging #74 into master will decrease coverage by 0.02%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master      #74      +/-   ##
==========================================
- Coverage   98.59%   98.57%   -0.03%     
==========================================
  Files           2        2              
  Lines          71       70       -1     
==========================================
- Hits           70       69       -1     
  Misses          1        1
Impacted Files Coverage Δ
lib/plugin.js 98.55% <100%> (-0.03%) ⬇️

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 c84f3f8...bff4cb0. Read the comment docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

basePath should only be used to update the key
2 participants