Rework of rules properties

[milbrandt]

• rules of severity info in 1.0.6.110 reset from Major to info, see issue several rules are showing as deprecated #57
• use constrants from org.sonar.api.rule.Severity instead of strings
• some refactoring

Open Points:

• In org.sonar.plugins.fsharp.FSharpSonarRulesDefinition there are 16 additional rules which are not activated in FSharpSonarWayProfile. Some of them should IMHO included, eg RulesRedundantNewKeyword Why are These rules not included? Any history behind it? These rules are unchanged for now.
• RuleProperty - Constructor and getters or a pure bean with getters and setters.
• Missing HtmlDesicription of the rules are in sonar-fsharp-plugin\src\main\resources\org\sonar\l10n\fsharp\rules?
• why set priority in org.sonar.plugins.fsharp.FSharpSonarWayProfile.activateRule as it is already set in FSharpSonarRulesDefinition while creating the rules?

@jmecosta Feel free to commit to this branch on any of the above open points

[milbrandt]

@jmecosta Any comments on my questions in the initial PR? Especially question 1, 3, 4 I don't know the background.

[jmecosta]

The asnwer is pretty much the same, the rules have not ever been stabilized and i supose after of both sonar and fsharp lint those have just become outdated. My sughestion is we take what fsharp lint provides now and go with it. Hrmldescriptiosn i have no idea what to put there, i would rather just not have everything

[milbrandt]

I would like to merge this PR and have created a new issue to sync rules between FshapLint and this plugin.

[jmecosta]

they can go, Fsharp.Lint doest produce those anymore and users cant use another version of fsharplint

[milbrandt]

As this branch still uses id="FSharpLint.Core" version="0.7.6" I was not sure. In net472 branch definitely.

[milbrandt]

All Xml-Rules are gone in current FSharpLint 0.12.1, the Hint-Rules are still in IMHO.

[jmecosta]

As this branch still uses id="FSharpLint.Core" version="0.7.6" I was not sure. In net472 branch definitely.

the current master imo is still WIP, only after we have net472 in place i think we can stabilize the version. At least i wouldnt do any major release of the current master

[milbrandt]

I would like to release 1.0.6 officially with net45, removed deprecated API and hopefully my repoting issue (I haven't started looking on it yet). Then the current master would be good for SonarQube 8.
All other stuff only in net472 branch, Accord.

[jmecosta]

If the current rule set is ok then i dont see why not. Your reporting issue does seem more critical atm

…

On Thu, 20 Jun 2019, 21:02 Volker Milbrandt, ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In sonar-fsharp-plugin/src/main/java/org/sonar/plugins/fsharp/FSharpRuleProperties.java <#61 (comment)> : > + + // Typography + rules.put("RulesTypographyTrailingLineError", new RuleProperty(Severity.MAJOR, "File should not have a trailing new line", "<p></p>")); + rules.put("RulesTypographyTabCharacterError", new RuleProperty(Severity.MAJOR, "Tabulation character should not be used", "<p></p>")); + rules.put("RulesTypographyFileLengthError", new RuleProperty(Severity.MAJOR, "File should not have too many lines", "<p></p>")); + rules.put("RulesTypographyLineLengthError", new RuleProperty(Severity.MAJOR, "Lines should not be too long", "<p></p>")); + rules.put("RulesTypographyTrailingWhitespaceError", new RuleProperty(Severity.MAJOR, "Lines should not have trailing whitespace", "<p></p>")); + + // nested statements + rules.put("RulesNestedStatementsError", new RuleProperty(Severity.MAJOR, "Maximum allowed of nesting", "<p></p>")); + + // hint matcher - todo Map of list + rules.put("RulesHintRefactor", new RuleProperty(Severity.MAJOR, "Hint Refactor", "<p></p>")); + rules.put("RulesHintSuggestion", new RuleProperty(Severity.MAJOR, "Hint Suggestion", "<p></p>")); + + rules.put("RulesXmlDocumentationExceptionError", new RuleProperty(Severity.INFO, "deprecated rule", "<p></p>")); I would like to release 1.0.6 officially with net45, removed deprecated API and hopefully my repoting issue (I haven't started looking on it yet). Then the current master would be good for SonarQube 8. All other stuff only in net472 branch, Accord. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#61>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAH6HSGW4VJZXMDZ4JTMGUDP3PA3LANCNFSM4HYRSIKQ> .