Invalid sets of presets should throw a preset diagnostic
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
No files, tests, or entry points are named. Locate the preset validation path and its existing per-value diagnostic, then determine how invalid combinations are represented and add coverage for an invalid set of preset values; done means the whole preset fails with a preset diagnostic.
Written by the indexing model from the issue text.
Description
If a preset has an invalid set of values, it should fail. Right now we only check if each individual value is valid against it's parameter.
But the preset as a whole (set of inputs) could be invalid.
- Dominant language
- Go
- Stars
- 9
- Forks
- 5
- Avg merge
- 5d 17h
- Merged PRs (30d)
- 5
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.
More from coder/preview
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
bug
-
upstream
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 60/100
github/gh-aw-mcpg#13748 ·
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
googleapis/librarian#7670 · 2 comments ·