Multiple statements with flags
Open
Nobody has claimed this yet.
linter
- Dominant language
- JSON
- Stars
- 5.8k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 186
Description
I managed to accidentally have the following in a PR:
"safari": [
{
"version_added": "16"
},
{
"version_added": "preview",
"flags": [
{
"type": "preference",
"name": "CSS overflow: clip support"
}
]
}
],
This is somewhat clearly nonsense.
Per our logic, preview > 16, and it doesn't make sense for it to be added in 16, and also added in a later version behind a flag without being removed from the earlier version.
This should also be raising an error due to the ordering, given preview > 16.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the validation logic that checks compatibility statement ordering and flag usage, then reproduce the Safari data shown in the issue. Done means the invalid combination is rejected with an error for the ordering and multiple statements with flags.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100