Slither-log
- Dominant language
- Python
- Stars
- 6.4k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
Create a tool for debugging hardhat project that
- Add `console.log` at every function/modifier entry point, with the canonical name of the function, and the function parameters
- Add `console.log` at every end of the function/modifier, with the canonical name of the function, and the return values
Potential flags
- `--only contract/function`
- `--exclude contract/function`
- `--force-patch` patch the codebase directly (default behavior would probably to create a git patch)
Contributor guide
Research direction
No files, tests, or entry points are named in the issue. Start by locating Slither's command-line entry point and its handling of Hardhat projects, then define the patch-generation flow, function/modifier logging, filtering flags, and what output should confirm completion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, solidity
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100