Details

    • Type: Improvement Improvement
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 1.4.0
    • Component/s: None
    • Labels:
      None
    • Number of attachments :
      0

      Description

      CodeNarc rules are now being part of code quality checking both inside IntelliJ IDEA and as part of the gradle build.
      The active rules should be tweaked to allow/disallow useful rules.

        Activity

        Hide
        Vaclav Pech added a comment -

        Inspiration can be taken from codenarc config for groovy - http://svn.codehaus.org/groovy/trunk/groovy/groovy-core/config/codenarc/codenarc.groovy

        Show
        Vaclav Pech added a comment - Inspiration can be taken from codenarc config for groovy - http://svn.codehaus.org/groovy/trunk/groovy/groovy-core/config/codenarc/codenarc.groovy
        Hide
        Vaclav Pech added a comment -

        Since GPars is mostly written in Java, while the tests and demos in Groovy, we should either have separate codenarc profiles for both 'main' and 'test' source sets or tailor the profile for demos - e.g. println statements, empty catch blocks, unused variables, explicit return are all fine most of the time, for example.

        Show
        Vaclav Pech added a comment - Since GPars is mostly written in Java, while the tests and demos in Groovy, we should either have separate codenarc profiles for both 'main' and 'test' source sets or tailor the profile for demos - e.g. println statements, empty catch blocks, unused variables, explicit return are all fine most of the time, for example.

          People

          • Assignee:
            Vaclav Pech
            Reporter:
            Vaclav Pech
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated: