oxidecomputer / oxidecomputer/openapi-lint
catch confusing use of case in identifiers
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 12
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
See oxidecomputer/omicron#2868. Maybe we could catch identifiers in the spec like a_b_c? Or single-letter words?
Contributor guide
No contributing guide indexed for this repository
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 with the referenced oxidecomputer/omicron#2868 issue to understand the confusing identifier cases. The payload names no files or tests, so the accepted identifier patterns and the repository location for adding and testing a lint rule must be established before implementation; done means the intended cases are agreed and validated by the linter.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi, rust
- Domain
- backend-api-design, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100