-
-
Notifications
You must be signed in to change notification settings - Fork 158
Conversation
5cfd3b4
to
0e43108
Compare
Maybe semverify all targets' versions immediately? If there are no difference between '5' and 5, why we should log it as a different values? Also it would be good for the |
"Few" more changes:
|
3de93ac
to
9f0f104
Compare
Codecov Report
@@ Coverage Diff @@
## 2.0 #231 +/- ##
======================================
Coverage ? 94.61%
======================================
Files ? 6
Lines ? 223
Branches ? 64
======================================
Hits ? 211
Misses ? 9
Partials ? 3
Continue to review full report at Codecov.
|
@@ -245,20 +245,22 @@ const generateData = (environments, features) => { | |||
environments.forEach(env => { | |||
const version = getLowestImplementedVersion(options, env); | |||
if (version !== null) { | |||
plugin[env] = version; | |||
plugin[env] = version.toString(); |
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.
Should we semverify
these?
c3a0e75
to
223ae49
Compare
259215a
to
6d32f1d
Compare
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.
we can drop _extends and just use Object.assign in 2.x (another pr is fine)
First part of #187.
Wanted to keep it relatively small, so only the following changes:
semverify
and moved_extend
to utils file ala [WIP] Add node's "engines" option #114build-data
now outputs string values for env versionssemver
to check if a plugin is required"node": 6.9
and target"node": 6.10
will behave differently) with numeric target versions, not sure if we should drop in 2.0?We should follow this up with #114 then possibly add range support to targets (
"chrome": "^52"
) if we want.