-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
add-new-bcd: filters needed #788
Comments
The reason that Additionally, I personally think that it would be better to run |
Yes, I see that it must collect info on all browsers but my use case is to create a PR for a new browser release like mdn/browser-compat-data#21083.
In this case all browsers would be false but Firefox would be 120. In this scenario I'm not interested in new features that are shipping in Chrome 122 and are false in all other browsers, for example. Does that make sense? |
For mdn/browser-compat-data#21148 I had to manually filter out the new stuff in Chrome 120. Would have loved if there was a filter. |
I've worked through almost all of the things that add-new-bcd proposes and I opened PRs to improve the test-builders. I think if these are merged the list of things add-new-bcd proposes should be fairly small, so maybe filters aren't needed then after all. |
I need the same filtering that
update-bcd
has in theadd-new-bcd
script:Right now I can do:
npm run update-bcd -- -b firefox -r 120-120
But not:
npm run add-new-bcd -- -b firefox -r 120-120
The text was updated successfully, but these errors were encountered: