oxidecomputer / oxidecomputer/omicron
want database schema validator
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
We could catch issues like #1533. More generally, we could validate:
- names, types, nullability, and uniqueness for standard fields (like id, name, time_created, time_modified, time_deleted)
- uniqueness of indexes (see #1497 -- unclear if this could be a hard rule)
- singular vs plural?
- snake case vs. camel case?
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 reviewing issues #1533 and #1497; the issue names no file, test, or entry point. Done would require an agreed validator scope and rules for standard-field names, types, nullability, uniqueness, index uniqueness, and naming conventions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100