This repository has been archived by the owner on May 11, 2018. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 158
no node7 rules. node -> chrome version aliases miss gaps #45
Labels
Comments
you can make a pr if you'd like for those, otherwise will close then? |
I'm just saying the alias algorithm is wrong |
It's wrong? I'm not clear on what you mean - do we need to make a pr to compat-table? |
Can you explain this again? I'm afraid I didn't understand the issue? |
in compat table: function interpolateResults(res) {
var browser, prevBrowser, result, prevResult, bid, prevBid;
for (bid in rawBrowsers) {
// For browsers that are essentially equal to other browsers,
// copy over the results.
browser = rawBrowsers[bid];
if (browser.equals && res[bid] === undefined) {
result = res[browser.equals];
res[bid] = browser.ignore_flagged && result === 'flagged' ? false : result;
// For each browser, check if the previous browser has the same
// browser full name (e.g. Firefox) or family name (e.g. Chakra) as this one.
} else if (prevBrowser &&
(prevBrowser.full.replace(/,.+$/,'') === browser.full.replace(/,.+$/,'') ||
(browser.family !== undefined && prevBrowser.family === browser.family))) {
// For each test, check if the previous browser has a result
// that this browser lacks.
result = res[bid];
prevResult = res[prevBid];
if (prevResult !== undefined && result === undefined) {
res[bid] = prevResult;
}
}
prevBrowser = browser;
prevBid = bid;
} flattens all previous browsers and equal browsers flags onto the new browser. your ./scripts/build-data.js only looks at the first browser after an equals, eg node7 should include all the changes of chrome54, chrome53, chrome52. Instead you only look at chrome54 |
graingert
added a commit
to graingert/babel-preset-env
that referenced
this issue
Dec 12, 2016
graingert
added a commit
to graingert/babel-preset-env
that referenced
this issue
Jan 19, 2017
graingert
added a commit
to graingert/babel-preset-env
that referenced
this issue
Jan 19, 2017
graingert
added a commit
to graingert/babel-preset-env
that referenced
this issue
Jan 19, 2017
hzoo
added
closed: from-preset-env
pkg: preset-env
and removed
closed: from-preset-env
labels
Oct 5, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently the version aliases are:
note that chrome53 and chrome52 are missing. This means that any rule, eg async-functions does not include those changes.
This is currently fine because all those changes are covered by flags
The text was updated successfully, but these errors were encountered: