Closed fbac closed 2 months ago
The changes optimize the Slither analysis by targeting it solely on v2 contracts located in the contracts/prototypes
directory and excluding legacy contracts in the contracts/evm
and contracts/zevm
directories. This adjustment ensures Slither is run only where needed, enhancing efficiency.
File | Change Summary |
---|---|
.github/workflows/slither.yaml | Added target: contracts/prototypes to the Slither workflow configuration. |
slither.config.json | Updated filter_paths to include contracts/evm and contracts/zevm , excluding them from analysis. |
Objective (Issue #) | Addressed | Explanation |
---|---|---|
Run Slither only for v2 contracts (#228) | ✅ | |
Skip running Slither for legacy contracts (#228) | ✅ |
In the land where code does spring,
Slither now has found its ring.
For v2 it casts its gaze,
Ignoring the old in its maze.
Efficiency blooms, the new it scans,
Hopping forward with its plans.
🌟🐇✨
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
@skosito can you check this one sometime?
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 58.29%. Comparing base (
2bbd352
) to head (df1eb0f
).
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Closes https://github.com/zeta-chain/protocol-contracts/issues/228
Summary by CodeRabbit