Menu

#11 More extensive coding standard

0.5
open
3
2017-05-06
2010-07-10
No

More extensive coding standard.

Discussion

  • Jan Magne Tjensvold

    • assigned_to: nobody --> evild00d
     
  • Jan Magne Tjensvold

    I have a bit of experience from another project using StyleCop to enforce a coding standard so this task suits me well.

     
  • Jan Magne Tjensvold

    Will try to trim down the number of exclusions in Settings.StyleCop to the bare minimum by making the code conform to the StyleCop rules.

     
  • Jan Magne Tjensvold

    Current StyleCop rule progress:
    - Documentation rules just started.
    - Layout rules just started.
    - Maintainability rules almost complete. Only missing the private field rule (SA1401).
    - Naming rules almost complete. Only missing the lower case field name rule (SA1306).
    - Ordering rules in progress. Most of the element ordering rules remains.
    - Readability rules completed.
    - Spacing rules completed.

     
  • Jan Magne Tjensvold

    Naming rules complete.

     
  • Daniel Vale

    Daniel Vale - 2017-04-29
    • Priority: 6 --> 3
     
  • Daniel Vale

    Daniel Vale - 2017-04-29

    Confirmed: Style Cop errors need to be fixed for 0.5

     
  • Daniel Vale

    Daniel Vale - 2017-05-06

    I have turned off spacing rules 1003 and 1008 as they force there to be no spacing around the logical negation symbol, which hides it and makes the logic harder to decipher.

    ie StyleCop wants:
    if (!LogicToBeNegated) NoViolation();

    I preffer:
    if ( ! LogicToBeNegated) NoViolation();

    Unfortunately this will not enforce the preferred layout, just allow it.

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.