duneanalytics / duneanalytics/evm.codes
Playground: do not cut values on the stack
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 827
- Forks
- 199
- Avg merge
- 15m
- Merged PRs (30d)
- 1
Description
I think it would be more convenient if the values in the stack will not be truncated, e.g. PUSH1 0x42 would output in stack not just 42 but 0000000000000000000000000000000000000000000000000000000000000042, i.e. with a size of 32 bytes.
If my suggestion does not suit you, let me know.
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 at the Playground stack display and locate where stack values are currently truncated. Trace the rendering path for a PUSH1 value such as 0x42, then verify that displayed values use 32-byte zero padding without changing the underlying value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- blockchain, frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100