Bug: Error handling is unclear when account creation fails
- Dominant language
- TypeScript
- Stars
- 172
- Forks
- 207
- Avg merge
- 49m
- Merged PRs (30d)
- 1
Description
### Describe the bug
When creating a new account using the Base Account SDK, the error messages aren’t very clear. It’s hard to understand exactly what went wrong, which makes troubleshooting frustrating. The error could be caused by missing information, invalid input, or something else, but it’s not easy to tell from the message
### Steps
1. Try creating an account using the SDK with incomplete or invalid information.
2. The SDK throws an error, but the message doesn’t explain what’s wrong.
3. Troubleshoot to figure out what needs to be fixed.
### Expected behavior
The SDK should provide a clear and detailed error message that explains what went wrong during account creation.
### Version
_No response_
### Additional info
Improve the error handling to give more specific feedback on what caused the failure. For example, if a required field is missing or the data format is wrong, the error should point that out clearly
### Desktop
Tested on macOS using Node.js LTS during local development
### Smartphone
_No response_
Contributor guide
Research direction
Start by reproducing account creation with incomplete and invalid information using the Base Account SDK on Node.js LTS, then trace the account-creation error path. Define and verify messages that identify missing required fields and invalid data formats, with tests covering those failure cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100