oxidecomputer / oxidecomputer/v-api
Access groups should have a description
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 8
- Forks
- 5
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 59
Description
Add an optional internal description field to access groups.
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 by locating the access-group API and its model or schema definitions in this Rust repository. Check how access groups are represented and exposed, then verify that an optional internal description is accepted and returned where appropriate; the issue names no tests, so identify the relevant API test entry point before confirming the change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100