libcord-tech / libcord-tech/gauntlet
Shortening list of switchers can prep "undefined"
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
I think what's going on is that we don't set the currentswitcher storage value when a user updates the list of switchers in the settings — so if the current switcher index is greater than the new length, accessing the (non-existent) value at that index returns undefined.
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 in the settings flow that updates the list of switchers and inspect how the currentswitcher value is stored and read. Reproduce the issue by shortening the list while the selected index is out of range; done when accessing the current switcher no longer produces undefined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100