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

Add accepts_flags to the browsers schema as an optional hint #11286

Merged
merged 2 commits into from
Aug 17, 2021

Conversation

ddbeck
Copy link
Collaborator

@ddbeck ddbeck commented Jun 28, 2021

Summary

This PR proposes an addition to the schema, accepts_flags for both browsers as a whole and individual releases. This is me trying to having it both ways: providing an easy option (per-browser) for easy cases and a harder option (per-release) for harder cases.

I defined this part of the schema as an optional hint, rather than to trying to use it to drive the linter immediately or do anything more restrictive. I'm proposing it in this shallow state now, so that we can roll it into the next breaking release (which we require for schema changes).

Related issues

#10616

@ddbeck ddbeck requested a review from Elchi3 June 28, 2021 14:54
@github-actions github-actions bot added data:browsers Data about browsers (versions, release dates, etc). This data is used for validation. docs Issues or pull requests regarding the documentation of this project. schema Isses or pull requests regarding the JSON schema files used in this project. labels Jun 28, 2021
@ddbeck ddbeck added the not ready This is not yet ready to be merged. It's pending a decision, other PR, or a prerequisite action. label Jun 28, 2021
@ddbeck
Copy link
Collaborator Author

ddbeck commented Jun 28, 2021

(Flagged as not ready, so we don't merge it before the next breaking release, likely to take place in July.)

Copy link
Member

@Elchi3 Elchi3 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like this approach 👍

Copy link
Collaborator

@queengooborg queengooborg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I love this approach as well, so much cleaner than just putting the data into a linter, allowing for our consumers to easily utilize the data too!

@ddbeck ddbeck added this to the v4.0.0 milestone Aug 17, 2021
@ddbeck ddbeck removed the not ready This is not yet ready to be merged. It's pending a decision, other PR, or a prerequisite action. label Aug 17, 2021
@ddbeck
Copy link
Collaborator Author

ddbeck commented Aug 17, 2021

Since this is approved and I'm planning for the next release (Thursday) to be v4.0.0, I'm merging this now.

@ddbeck ddbeck merged commit 8cf15c4 into mdn:main Aug 17, 2021
@ddbeck ddbeck deleted the accepts_flags branch August 17, 2021 14:03
ddbeck added a commit to ddbeck/browser-compat-data that referenced this pull request Aug 17, 2021
ddbeck added a commit that referenced this pull request Aug 19, 2021
* Bump version to v4.0.0

* Add release note for #11234

* Bump known issues

* Add release note for #11760

* Add release note for #11286

* Add release note for #9830

* Add release note for #10334

* Add v4.0.0 highlights to release notes

* Add release note for #10753

* Revise description of `accepts_flags` hint

* Add release note for #11961

* Add release note for #12059

* Add stats
@queengooborg
Copy link
Collaborator

I'm opting to remove the release-level property in #15990 because of a lack of implementation. We've only been using the browser-level version in practice and in linting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data:browsers Data about browsers (versions, release dates, etc). This data is used for validation. docs Issues or pull requests regarding the documentation of this project. schema Isses or pull requests regarding the JSON schema files used in this project.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants