SA1516: misfire in C# 9 top-level statements

[AArnott]

Given this Program.cs file:

// Copyright (c) Andrew Arnott. All rights reserved.
// Licensed under the MIT license. See LICENSE file in the project root for full license information.

using MinerForeman;

var foreman = new Foreman();
await foreman.RunAsync();

The last line in the file above produces:

Warning	SA1516	Elements should be separated by blank line	Program.cs

This repros with StyleCop.Analyzers 1.2.0-beta.333

[thomaslevesque]

I'm seeing this as well. Apparently all top-level statements must be separated by a blank line, otherwise I have this warning.

What's weird is that the diagnostic doesn't report any file location... I have a warning, but I don't know where.

[sharwell]

@thomaslevesque The reporting location bug is #3242, and should be fixed in newer releases.

[thomaslevesque]

@sharwell thanks. Yes, I probably need to update to a newer version.

[msmolka]

What is the status of this issue? do you know maybe in which pre-release it will be done? I'm using 1.2.0-beta.406 and still seeing issue on top=level statements

[sharwell]

I don't believe anyone has submitted a fix for this issue yet.

[madhusameena]

Any comments on this ?
or any workaround for this ?

[maxkoshevoi]

I don't believe anyone has submitted a fix for this issue yet.

@sharwell Created a fix: #3482

[maxkoshevoi]

@sharwell Thanks for merging so quickly! Is there an ETA on next NuGet release?

[domagojmedo]

Still not fixed in 1.2.0-beta.406

[ultimaweapon]

That one is released before #3482 is merged.

[sharwell]

Yep, waiting for a few more items to finish/merge and the next release should be soon.