Right clicking to supress on a warning from a generated file does not suppress it.

[chsienki]

A warning introduced by a source generated file will show in the error list, and the user can right click to choose the suppression level.

However, when applying the suppression it is added to the .editorconfig file, which will not have any affect on the generated code. Thus it continues to appear.

The correct solution (currently) would be to add the supression in a .globalconfig so that it also applies to generated code. This has the downside however of applying to all source files in the solution, which is obviously not an ideal solution either.

[chsienki]

@mavasani @jmarolf

[chsienki]

We're back in the somewhat crummy situation where a .globalconfig is too strong, and and .editorconfig doesn't apply to generated code.

I think we need to tweak the design (again 😕) to either somehow allow .editorconfig to apply to generated code, or allow .globalconfig to support wildcards. I think i'd prefer the first option, as the more we can keep things out of the global config the better, but we'd need to design something for it.

[jmarolf]

These warnings should not be reported in the first place. are these files not marking themselves as generated code?

[chsienki]

@jmarolf Filed alongside the following: #54119