OpenZeppelin / OpenZeppelin/compact-tools
Improve private state setters
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 5
- Avg merge
- 15h 28m
- Merged PRs (30d)
- 31
Description
Currently, we have setPrivateState and updatePrivateState...a better approach would be to consolidate => setPrivateState(prev => ({ ...prev, secretField: 1n })) (think react hooks)
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 by locating the implementations and callers of setPrivateState and updatePrivateState in the repository, then read their tests or usage examples if present. Clarify the intended consolidated setter behavior and update the relevant coverage so done means the existing private-state updates still work through the new approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100