Inheritance graphs in SVG readability improvements
Open
bug-candidate
- Dominant language
- Python
- Stars
- 6.4k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
### Describe the issue:
Inheritance graphs in SVG can be confusing to read for large codebases. This can be mitigated with the following ideas:
* Remove Mock contracts from the graph: they are usually not audited directly
* Remove the private error node, which can be very large (and it is always disconnected from the rest?)
* Avoid using colors like yellow, which are difficulty to read when using white background.
* Optionally, allow to hide the interface contracts, to quickly identify where the code is defined
### Code example to reproduce the issue:
We already have this internally.
### Version:
Slither 0.8.3
### Relevant log output:
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.