Search Issue Tracker

Won't Fix



Found in




Issue ID




.editorconfig files are ignored when a Roslyn analyzer is running through the Editor



Reproduction steps:
1. Open the "" project
2. Observe the Console

Expected result: RCS1213 is thrown only once
Actual result: RCS1213 is thrown twice

Reproducible with: 2022.3.1f1, 2023.1.0b20, 2023.2.0a18
Could not test with: 2021.3.27f1 (No errors are thrown)

Reproducible on: Windows 10

Note: Error must be thrown once because the "roslynator_suppress_unity_script_methods" flag is set to “true” in the ".editorconfig" file but two errors are thrown because of the “Assets/Scripts/Scripts.ruleset” file

  1. Resolution Note:

    We do not currently support editorconfig files.

Comments (1)

  1. NoTuxNoBux

    Jun 08, 2023 12:50

    Bummer that it won't be fixed. I understand the reasoning, but this effectively results in our upgrade path to 2022.3 from 2021.3 being blocked, since we use Roslyn analyzers this way extensively (Roslynator doesn't even support configuring through XML any more in recent versions for some options) and in 2021.3 we could disable them in editor. Since the option to disable has been fully removed in 2022, we are blocked from entering play mode due to incorrectly reported errors.

    As a workaround we'll have to downgrade them to warnings or find another creative solution where we drop support for Unity's Roslyn analyzers and only load them in our IDE (for OmniSharp).

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.