OpenZeppelin / OpenZeppelin/openzeppelin-upgrades
Support adding variables at the end of storage gap
Open
Nobody has claimed this yet.
storage-checks
- Dominant language
- TypeScript
- Stars
- 658
- Forks
- 286
- PR merge metrics
- No merged PRs in 30d
Description
The current storage gap approach in the plugins allows variables to be inserted at the beginning of a gap. More generally, variables should be allowed to be inserted at the end of a gap as well.
Contributor guide
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
The issue does not identify files or tests; start by locating the plugins' existing storage-gap handling and how variables inserted at the beginning are validated. Implement support for variables at the end of a gap, then verify the relevant storage-layout checks cover both insertion positions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- solidity, typescript
- Domain
- blockchain, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100