SOLIDPOD: use specific exception subclass in `KeyManager`
Open
Nobody has claimed this yet.
- Dominant language
- Dart
- Stars
- 10
- Forks
- 7
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
Exception subclasses have been introduced in solidpod for
- user not logged in
- security key not available in local cache
- etc.
Please make use of these specific exceptions in KeyManager to provide more informative messages in case of errors (e.g., no longer prints user not logged in when a user has actually logged in but hasn't provided their security key which triggered an error).
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 KeyManager and the exception subclasses introduced in solidpod. Trace how login and security-key cache errors are currently handled, then verify that each relevant failure uses its specific exception and produces an informative message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart
- Domain
- authentication, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100