Resolve forge lint "custom-errors"
Open
- Dominant language
- Solidity
- Stars
- 20
- Forks
- 17
- Avg merge
- 2h 31m
- Merged PRs (30d)
- 4
Description
We prefer to define typed errors rather than using `Error(string)` (also naked reverts) because this reduces codesize.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by running the forge lint check for custom-errors and review each reported Error(string) or naked revert. Done means the lint finding is resolved by using typed errors while preserving the existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- solidity
- Domain
- blockchain
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100