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: make extractComments API more consistent #129

Merged

Conversation

alexander-akait
Copy link
Member

This PR contains a:

  • bugfix
  • new feature
  • code refactor
  • test update
  • typo fix
  • metadata update

Motivation / Use-Case

fixes #20

Breaking Changes

Yes

BREAKING CHANGE: using the extractComments.condition option with true value extract only some comments

Additional Info

No

BREAKING CHANGE: using the `extractComments.condition` option with `true` value extract only `some` comments
@alexander-akait alexander-akait merged commit 37d2df0 into master Sep 2, 2019
@alexander-akait alexander-akait deleted the fix-make-extractComments-API-more-consistent branch September 2, 2019 17:54
@codecov
Copy link

codecov bot commented Sep 2, 2019

Codecov Report

Merging #129 into master will increase coverage by 0.02%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #129      +/-   ##
==========================================
+ Coverage   98.58%   98.61%   +0.02%     
==========================================
  Files           5        5              
  Lines         283      288       +5     
  Branches      113      117       +4     
==========================================
+ Hits          279      284       +5     
  Misses          4        4
Impacted Files Coverage Δ
src/minify.js 100% <100%> (ø) ⬆️

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 edbd3e0...6f584db. Read the comment docs.

sodatea added a commit to sodatea/vue-cli that referenced this pull request Oct 11, 2019
BREAKING CHANGE:
The only real breaking change is webpack-contrib/terser-webpack-plugin#129,
which is not likely to affect normal users.

The rest are default option values changes, which are already covered in
the default provided `terserOptions` of Vue CLI.

Note that here we choose to disable `extractComments` by default, as I
don't see enough data showing such license comments taking too much
space. The extra LICENSE file may also be confusing to some users.
sodatea added a commit to vuejs/vue-cli that referenced this pull request Oct 11, 2019
BREAKING CHANGE:
The only real breaking change is webpack-contrib/terser-webpack-plugin#129,
which is not likely to affect normal users.

The rest are default option values changes, which are already covered in
the default provided `terserOptions` of Vue CLI.

Note that here we choose to disable `extractComments` by default, as I
don't see enough data showing such license comments taking too much
space. The extra LICENSE file may also be confusing to some users.
ZanderOlidan pushed a commit to ZanderOlidan/vue-cli-service-chalkfix that referenced this pull request Feb 5, 2024
BREAKING CHANGE:
The only real breaking change is webpack-contrib/terser-webpack-plugin#129,
which is not likely to affect normal users.

The rest are default option values changes, which are already covered in
the default provided `terserOptions` of Vue CLI.

Note that here we choose to disable `extractComments` by default, as I
don't see enough data showing such license comments taking too much
space. The extra LICENSE file may also be confusing to some users.
ZanderOlidan pushed a commit to ZanderOlidan/vue-cli-service-chalkfix that referenced this pull request Feb 5, 2024
BREAKING CHANGE:
The only real breaking change is webpack-contrib/terser-webpack-plugin#129,
which is not likely to affect normal users.

The rest are default option values changes, which are already covered in
the default provided `terserOptions` of Vue CLI.

Note that here we choose to disable `extractComments` by default, as I
don't see enough data showing such license comments taking too much
space. The extra LICENSE file may also be confusing to some users.
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.

Make extractComments API more consistent
1 participant