SOLIDPOD: unify error handling - returning error code or throw exception
Open
Nobody has claimed this yet.
- Dominant language
- Dart
- Stars
- 10
- Forks
- 7
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
Two error handling approaches have been used in solidpod
- Return error code (e.g.,
SolidFunctionCallStatus.fail) - Throw a specific exception (e.g.,
AccessFailedException)
Please unify the error handling approach so that apps based on solidpod will have a consistent way to deal with errors occurred in solidpod API.
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
The issue names no files or tests. Start by cataloging where SolidFunctionCallStatus.fail and AccessFailedException are used across the solidpod API, then determine and document the single error-handling contract. Done means apps using solidpod have one consistent way to handle API errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart
- Domain
- api, backend-api-design
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100