Remove .editorconfig from distributed package

[fastict]

JetBrains Rider Editor 3.0.36
com.unity.ide.rider@4d374c7eb6db contains a .editorconfig, which prevents a project from ignoring messages that are triggered by this package.

See the sshot attached for the messages that are triggered by this project.
I have these messages suppressed in my project, but since your package contains its own .editorconfig, it override my settings.

I would like to achieve 0 messages in my project to identify new messages as they are introduced.

The workaround I've been using is going into \Library\PackageCache\com.unity.ide.rider@4d374c7eb6db and manually removing .editorconfig. However, this file is restored if a re-import or version upgrade happens.

Ideally, you ship a package that doesn't include an .editorconfig. Hoping this is a change that can be made.
Thanks

[van800]

If I understand correctly root = true in the https://github.com/van800/com.unity.ide.rider/blob/master/Packages/com.unity.ide.rider/.editorconfig
is a problem for you.

However, given you are in VS (my guess from the screenshot), why do you even have a csproj generated for the Rider package?

[fastict]

If I understand correctly root = true in the...

I can confirm that removing 'root = true' from the .editorconfig will suppress the messages (essentially the same as deleting it). However, as mentioned, the file will get restored upon any library refresh or version upgrade.

why do you even have a csproj generated for the Rider package?

I guess that's a fair question. It's a couple of things.

By default, on a new Unity project, the Unity Engineering package is installed (https://docs.unity3d.com/6000.1/Documentation/Manual/DeveloperToolsFeature.html ). This package has the Rider package as a dependency, so Rider is installed by default.
We work with a number of groups, and are creating new Unity projects all the time. We would prefer to avoid being in a situation where upon every new project, the first step is to remove a built-in Unity package.

Additionally, we work with different groups with different team configurations. Some groups and developers do work in Rider, and others use VS. We would like to cater to everyone's preferences, but at the same time, not introduce warnings and messages unecessarily.

Thanks for your consideration.

[van800]

I mean that generating csproj files for registry packages doesn't make much sense, you are not supposed to edit those anyway. There should be a checkbox for that in the Visual Studio package for Unity.

[fastict]

Oh I see what you mean. You are referring to the 'External Tools' section in Preferences.

We have the 'Registry packages' option checked, We supply our own registry packages to our teams. This is how we distribute common code shared across projects. So, we check that box so that we can view and debug our own packages. Unfortunately, this also generates a project for Rider.

Ideally I agree, I don't want to see the Rider package in VS, I don't need to be messing with that code.

However, Unity doesn't make a distinction between packages such as Rider and our own packages that we distribute. See here:
https://docs.unity3d.com/Packages/com.unity.ide.visualstudio@2.0/manual/using-visual-studio-editor.html

Registry packages | Any package that you install from either the official Unity registry or a custom registry. Packages in the Unity registry are available to install directly from the Package Manager.

[van800]

Would you please check, if adding [com.unity.ide.rider/.editorconfig] solves the problem for you?

[*.cs]
dotnet_analyzer_diagnostic.severity = none

I think we can add this, since it only affects VS, not Rider.

[fastict]

Yes, I can confirm that adding the suggested lines to Rider's .editorconfig successfully suppresses the VS messages for Rider.

[van800]

I have pushed this change in the feature branch, we will discuss it later with some other collegues to be sure there is no downsides.

[fastict]

Thanks, really appreciate it!