Type resolution has been enabled by default for all rules extending AbstractJavaRule for a while. The only place where the typeresolution attribute needs to be mentioned in XML is for XPath rules, which extend directly AbstractRule. This behaviour is surprising, and as pointed out in pmd/pmd-designer#28, the designer wasn't aware of it.
So instead of making the designer add a typeresolution='true' attribute, I would rather remove the need for it altogether before 7.0.0. Java is the only language that supports type resolution anyway, and the XML attribute as well as the method on the Rule interface will disappear.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4