Use descriptive names for contracts and libraries The code base makes use of many different contracts, abstract contracts, interfaces, and libraries for inheritance and code reuse.
In principle, this can be a good practice to avoid repeated use of similar code.
However, with no descriptive naming conventions to signal which files would contain meaningful logic, codebase becomes difficult to navigate.
Use descriptive names for contracts and
- ConsenSys Audit Growth DeFi Finding 5.6
- Naming Convention & Readability
- Multiple Contracts
- Code Reuse & Naming
- Use Descriptive Names