Disallow consecutive partial_implementation statements on same track
Open
Nobody has claimed this yet.
blocked
linter
- Dominant language
- JSON
- Stars
- 5.8k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 186
Description
What type of issue is this?
Infrastructure issue
What is the issue?
The linter did not complain about multiple consecutive support statements with partial_implementation: true:
What behavior were you expecting?
In these cases, a single partial_implementation should be used, with notes explaining the different progression.
What version(s) of BCD is the issue present in?
- The current BCD release
- The current version of the
mainbranch
Do you have anything more you want to share?
Noticed in this PR.
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
Review api/GPU.json around the linked example and the discussion in pull request 28604. Trace the linter behavior for consecutive support statements with partial_implementation: true. Done means the linter rejects consecutive statements on the same track and permits one statement with notes describing progression.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100