1 comment (1 comment)0 reactions (0 reactions)0 assignees (0 assignees)Python4,769 stars (4,769 stars)886 forks (886 forks)batch import
good first issuehelp wantednew printer
Description
This issue does not include a description.
Contributor guide
- Tech stack
- python
- Domain
- testingblockchain
- Issue type
- feature
- DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
- 3
- Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
- half day
- Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
- fresh
- ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
- needs investigation
- Prerequisites
- Basic knowledge of SlitherUnderstanding of cheatcodes in Foundry/Hardhat
- Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
- 40
- Research direction
- First, examine existing printer implementations in Slither, such as the 'printers' directory in the repository. The goal is to create a new printer that lists usage of cheatcodes (e.g., vm.* in Foundry or hre.network in Hardhat). Review the Slither documentation on adding printers. Investigate how Slither's AST parsing handles Solidity code to detect cheatcode calls. The issue body is empty, so clarify with maintainers via a comment whether specific cheatcodes or patterns are expected. Look at similar issues or PRs for reference, like those implementing other printers.