oxidecomputer / oxidecomputer/console
Better copy on 403 than "Action not authorized"
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 228
- Forks
- 22
- Avg merge
- 19h 42m
- Merged PRs (30d)
- 32
Description
If someone tries to, e.g., delete a silo image when they don't have permission to do so, they will get a toast that says
Could not delete resource
Action not authorized
I think we could come up with something better here that conveys that this is about the user themselves not having the appropriate permission to do the thing. Arguably that's what "Action not authorized" means, but I don't think it's obvious enough. "Authorized" as we're using it is a technical term meaning a permission check.
Alternatives
- You don't have permission
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 in libs/api/errors.ts at lines 56-57 and inspect how the 403 error text is used for actions such as deleting a silo image. Choose clearer wording that makes the user's missing permission explicit, then verify the resulting toast shows the revised message instead of "Action not authorized".
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100