Support file scoped namespace declarations when generating code

[304NotModified]

🤔 What's changed?

Generated file scoped namespaces when set in .editorconfig

Normally "create" generates this:

namespace MyNamespace.StepDefinitions
{
    [Binding]
    public class CalculatorStepDefinitions
    {
        [Given("the first number is {int}")]
        public void GivenTheFirstNumberIs(int p0)
        {
            throw new PendingStepException();
        }

With

# C# files
[*.cs]
csharp_style_namespace_declarations = file_scoped:suggestion

We get this:

namespace MyNamespace.StepDefinitions;

[Binding]
public class CalculatorStepDefinitions
{
    [Given("the first number is {int}")]
    public void GivenTheFirstNumberIs(int p0)
    {
        throw new PendingStepException();
    }

In VS config:

⚡️ What's your motivation?

Keep the code style from the editorconfig.

🏷️ What kind of change is this?

• ⚡ New feature (non-breaking change which adds new behaviour)

♻️ Anything particular you want feedback on?

📋 Checklist:

• I've changed the behaviour of the code
  • I have added/updated tests to cover my changes.
• My change requires a change to the documentation.
  • I have updated the documentation accordingly.
• Users should know about my change
  • I have added an entry to the "[vNext]" section of the CHANGELOG, linking to this pull request & included my GitHub handle to the release contributors list.

---

This text was originally taken from the template of the Cucumber project, then edited by hand. You can modify the template here.

[304NotModified]

This is ready for review. I tested it locally and added snapshot tests :)

[gasparnagy]

I've scanned it through and it looks cool! I'll make a more detailed review during my holidays.

[304NotModified]

@gasparnagy polite bump. FYI I have tested this locally

[gasparnagy]

@gasparnagy polite bump. FYI I have tested this locally

Yes, sorry for the delay. It's on my list... Pretty busy for the rest of the week, so can check probably next week only.

[gasparnagy]

Sorry for the late review. This is nice, thx!

It has turned out, that the EditorConfigOptionsProvider implemetation was slightly incorrect, because when it used the CreateAdHocDocument path it has just picked the first project to make the ad-hoc document for. But in reality, if you query the editorconfig values through the "wrong" project, the configured values don't come through. So in the https://github.com/reqnroll/Reqnroll.ExploratoryTestProjects/tree/main/ReqnrollCalculator if I added the editorconfig to the Specs project then it could not query it thought the ReqnrollCalculator project, that was the first.

I think this problem was not discovered, because we usually queried it for a IWpfTextView which usually had a document anyway, so it rarely went to the CreateAdHocDocument path.

Anyway. I have added a heuristic to try choosing the right project based on the folder. With that it works.

[304NotModified]

Thanks!

[gasparnagy]

Released today in: https://github.com/reqnroll/Reqnroll.VisualStudio/releases/tag/v2026.1.477