Provide default UX for logging in when server responds 401
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 153
- Forks
- 46
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 7
Description
We have lots of login panels, but at the moment there are many cases in which the mashlib code puts a 401 error message into a status panel. It shouldn't really do that without giving the user a button to log in.
This needs to be coordinated with the 401 handling which the client or its successor does.
Possible solutions are for the developer to optionally pass in a place in the the DOM real estate which can be used for this. It could probably be used for 403 handling also, and other error displays.
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 tracing how mashlib handles 401 responses and places their messages in status panels, then review the existing login panels and the client or its successor's 401 handling. Done means 401 responses offer a login action instead of only an error message, with a coordinated approach for an optional DOM location and possible 403 reuse.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100