SA1516: Allow omitting blank lines between property/event accessors

[Blaisor]

Currently, SA1516 triggers a violation when a multiline property setter immediately follows a multiline getter without an empty line. While accessors are distinct elements, they are logically part of a single unit. In many professional codebases, including high-profile projects like Newtonsoft.Json, these accessors are kept together without separation to maintain visual cohesion. In fact, I have never seen a codebase where an empty line between a get and set is considered common practice.

public string Description
{
    get
    {
        return _description;
    }
    set // SA1516 triggered here
    {
        _description = value;
    }
}

Proposed change: modify SA1516 to allow (or provide a configuration to allow) omitting blank lines between:

• get and set accessors
• add and remove event accessors

Exception: when there is a comment line before the setter/remove.

[bjornhellander]

I am currently in limbo regarding this repository. I created it because progress had stopped in StyleCop.Analyzers, but Sam returned late last year and progress was good, but now he has been absent again so far this year. I am currently waiting to see what will happen to that repository, so will probaly only do bugfixes for the moment.

Regarding your actual request, I currently don't think this is something I would like to support. There is no right and wrong related to this and I think the current behavior is good enough. It does not require a blank line between single-line accessors and I think it is at least reasonable from a readability perspective to separate the two accessors when they are multi-line. Making it configurable adds complexity, which is not welcome either. Considering how long this rule has worked this way (don't even know when the original StyleCop was created), I currently don't see a reason to change this.