"GM SLint Extensions" are extensions made by German Morales to the Refactoring BrowserSLint. My name is there just because the changes allow you to write your own SLint rules without writting them on ParseTreeLintRule/BlockLintRule, so I hope anyone can make their own extensions, and I want to avoid conflicts. I know little about SLint, so if such feature is already available and I couldn't find it, please let me know.
What's included in the change set:
LintDialog changes to take into account subclasses of ParseTreeLintRule/BlockLintRule
GMSELintDialog: subclass of LintDialog with extensions:
allows selecting all subclasses of the already selected classes
allows selecting classes and class categories matching a search criteria (for example, "Morphic-*")
allows selecting classes and class categories matching a search criteria
Pending Requested SLint Features:
test for "self player == nil" instead of hasPlayer (dgd)
the same for "owner"
test for "~~ nil"¨, "~= nil", #ifNotNil:, #ifNil:, etc in all cases (dgd)
direct access of variables
could use cascade messages
bad variable name (names with only 1 letter, 1 letter and 1 number, xxxSomething, etc )
extend the #hasExtent to #hasAnyAccesor (dgd)
extend the rule named 'Uses "size = 0", "= nil", or "at: 1" instead of "isEmpty", "isNil", or "first"" (dgd)
at:2 -> second, at:3 -> third and so on
~~ nil, = nil, ~= nil
= 0, == 0, = 0.0 –> isZero
add here your request, I'll try to make you happy
Requested "utilities"
"categorize all uncategorized" for a set of classes (dgd)
"categorize ALL" methods like the superclass (dgd)
done by dgd in CodeAuditingTool.
spread down the method comment to uncommented (or commented) methods (dgd)
categorize the accessor in accessing (dgd)
categorize the #isFoo methods in testing (dgd)
comment the uncommented accessors (dgd)
TIPS: the context menu for changesets include some useful utilities like: check for uncommented methods, check uncommented classes, check for uncategorized methods, etc. (dgd)