brigadecore / brigadecore/brigade-dashboard
Improper Error Handling
Open
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
### Description
Taking an example of this async function, try{} catch{} is must with async/await. Otherwise, it will lead to unexpected behaviour.

Over Here, this.props functions should only be called on successful Login/Logout but right now it just changes the state.

Contributor guide
Research direction
Start by locating the async login/logout handler described in the issue and inspect where this.props functions are called relative to the operation result. Reproduce the failure path, then verify that those callbacks run only after successful login or logout and that the existing error behavior remains correct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100