Open code423n4 opened 2 years ago
Typo
Agree, will fix.
Maximum line length exceeded
Fair however we use a limit of 120 instead. I believe this is more readable since it prevents excessive wrapping, particularly in comment. This is enforced by our linter.
Unresolved TODO comments
Agree, will fix.
Missing param
Agree, will fix.
Typo
AddressLibrary.sol: L13
Remove repeated word
library
Long single line comments
In theory, comments over 79 characters should wrap using multi-line comment syntax. Even if somewhat longer comments are acceptable, there are cases where very long comments interfere with readability. Below are several instances of long comments that could be improved by wrapping, as shown:
MarketFees.sol: L148-151
Recommendation:
Similarly for the following:
NFTCollection.sol: L174-177
NFTCollectionFactory.sol: L35-36
Suggestion:
Similarly for the following:
NFTCollectionFactory.sol: L272-285
NFTCollectionFactory.sol: L308-323
NFTCollectionFactory.sol: L347-362
NFTCollectionFactory.sol: L425-431
NFTCollectionFactory.sol: L436-443
NFTCollection.sol: L71-77
NFTCollectionFactory.sol: L57-61
Suggestion:
Comments concerning unfinished work or open items
Comments that contain TODOs or other language indicating open items should be addressed and modified or removed. Below are two instances:
MarketFees.sol: L193
MarketFees.sol: L284-285
Missing
@param
statementMarketFees.sol: L79-93
@param
statement is missing for_assumePrimarySale