-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Add <output>
element
#1442
Add <output>
element
#1442
Conversation
@petele if you're not getting the same results locally as the CI, it's probably because compute-baseline JS files haven't been updated. Running npm install inside packages/compute-baseline should fix it. @ddbeck can we avoid this someone? As for the range symbol, the problem is that BCS data about Edge is uncertain and affects the date. We'll need to test this in Edge and update BCD to be sure an out the correct dates. |
I'm getting the same error locally as well, so its not just in the CI |
Oh... it could be that this is the first feature with a range on the date, and that fails in a weird way. We should either disallow it and fail with a clear message, or just handle it. |
Prompted by the error in web-platform-dx#1442
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.
I've opened #1496 to deal with the error here. I've also got a suggestion for the description.
Prompted by the error in #1442
Co-authored-by: Daniel D. Beck <daniel@ddbeck.com>
No description provided.