duneanalytics / duneanalytics/evm.codes
Remove fork from settingsContext.ts
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 827
- Forks
- 199
- Avg merge
- 15m
- Merged PRs (30d)
- 1
Description
Currently, we save the user settings in the browser's localStorage.
These settings include:
export enum Setting {
EditorCodeType = 'editor::codetype',
VmChain = 'vm::chain',
VmFork = 'vm::fork',
}
We should consider removing VmFork from here since this is somewhat a weird behavior. I'd imagine users would rather be on the latest fork by default instead of staying "stuck" on the last fork they manually chose.
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 settingsContext.ts and inspect the Setting enum, especially the VmFork entry and its localStorage handling. Check references to VmFork to identify the affected settings flow; done means fork selection is no longer persisted there and the latest fork can be used by default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 65/100