Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

`dotnet format style --verify-no-changes` fails with naming violations and unnecessary imports

Open Beginner friendly
  • Is something wrong?
#624 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 7 days

@nmummau is already working on this.

Since Oct 20, 2026.

  • #625 by @nmummau — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
80/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
csharp
Domain
tooling

Research direction

Start with the listed files: the four core library files with IDE1006 diagnostics and the five test files with IDE0005 diagnostics. Read the repository's .editorconfig and inspect the named fields, constructor parameter, and using directives; check how Analyzed.cs is compiled by the analyzer tests. Run dotnet format style --verify-no-changes from the repository root to confirm completion, then verify the analyzer tests still pass.

Written by the indexing model from the issue text.

Description

Describe the bug

Running the style verification command from the repository root reports IDE1006 naming violations in four core library files and IDE0005 errors in five test files. The source does not satisfy the repository's existing .editorconfig rules, causing the verification command to fail.

To reproduce

  1. Use an Eventuous checkout at revision 60a76433.

  2. From the repository root, run:

    dotnet format style --verify-no-changes

  3. Observe the naming warnings and unnecessary-using errors below.

Expected behavior

The command exits successfully without reporting style violations or requiring source changes. The existing analyzer tests should continue to pass.

Actual behavior

The command reports the following diagnostics. Paths are relative to the repository root; repeated diagnostics and project-path suffixes have been omitted for readability. Line numbers refer to the affected revision.

src/Core/src/Eventuous.Diagnostics/EventuousDiagnostics.cs(18,38): warning IDE1006: Naming rule violation: These words must begin with upper case characters: listener
src/Core/src/Eventuous.Persistence/ExpectedStreamVersion.cs(14,36): warning IDE1006: Naming rule violation: The first word, 'Value', must begin with a lower case character
src/Core/src/Eventuous.Serialization/EventSerializer.cs(13,30): warning IDE1006: Naming rule violation: Prefix '_' is not expected
src/Core/src/Eventuous.Shared/TypeMap/TypeMap.cs(51,25): warning IDE1006: Naming rule violation: Prefix '_' is not expected
src/Core/test/Eventuous.Tests.Shared.Analyzers/Analyzed.cs(4,1): error IDE0005: Using directive is unnecessary.
src/Postgres/test/Eventuous.Tests.Postgres/Subscriptions/GapSkipTimeoutTest.cs(5,1): error IDE0005: Using directive is unnecessary.
src/Postgres/test/Eventuous.Tests.Postgres/Subscriptions/GapAgeReleaseWhileRunningTest.cs(5,1): error IDE0005: Using directive is unnecessary.
src/Postgres/test/Eventuous.Tests.Postgres/Subscriptions/GapRemediationBeforeSkipTest.cs(5,1): error IDE0005: Using directive is unnecessary.
src/Sqlite/test/Eventuous.Tests.Sqlite/Metrics/MetricsFixture.cs(9,1): error IDE0005: Using directive is unnecessary.

Environment

  • OS: Linux
  • .NET SDK: 10.0.201
  • Solution: Eventuous.slnx
  • Affected projects target net10.0, net9.0, and net8.0; diagnostics repeat across target frameworks.

Additional context

The naming violations concern the static fields listener, _default, and _index, and the StreamReadPosition constructor parameter Value. The public Value property is separate from the constructor parameter.

Analyzed.cs is also loaded directly as source by the analyzer tests. Its System, System.Collections.Generic, and System.Threading.Tasks imports duplicate SDK implicit usings during a normal project build, but the standalone Roslyn compilation needs equivalent imports. Removing the redundant directives should preserve that test compilation context.

Dominant language
C#
Stars
512
Forks
99
Avg merge
5d 6h
Merged PRs (30d)
5

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Eventuous/eventuous

All issues in Eventuous/eventuous

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.