oxidecomputer / oxidecomputer/console
Help text on firewall rule name fields should explain name targeting
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 228
- Forks
- 22
- Avg merge
- 19h 42m
- Merged PRs (30d)
- 32
Description
Name matching is literally on the name — it is not resolved to an instance ID. You can set up a name target on a name that doesn't exist yet. You can delete the targeted thing and make a new one with the same name. The help text should convey this concisely somehow.
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 locating the firewall rule name fields and their current help text in the console UI. Revise the text to explain that matching uses the literal name, works before a target exists, and applies to a replacement with the same name; confirm both name fields present the concise explanation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100