Details

    • Type: Sub-task Sub-task
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: Lucene.Net 2.9.4, Lucene.Net 2.9.4g, Lucene.Net 3.0.3
    • Fix Version/s: Lucene.Net 3.0.3
    • Labels:
      None
    • Environment:

      all

      Description

      We should use .NET properties where ever possible. There are many methods in the API that use methods similar to Class.Getxxxxx() or Class.Setxxxxx(). These methods often just return a less-accessible field, with no real logic behind it.

      • If there are both public Get/Set methods with no special logic, they can be turned into an automatic property: Name { get; set; }
      • If there are both Get/Set methods with no special logic and the setter is private, use an automatic property: Name { get; private set; }
      • In other cases, use good judgement based with the amount of logic that is present in the getter and setter methods.

        Activity

        Christopher Currens created issue -
        Christopher Currens made changes -
        Field Original Value New Value
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]

          People

          • Assignee:
            Unassigned
            Reporter:
            Christopher Currens
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development