Config to hide errors that are not winning overrides

[Noggog]

Another thing to think about is topics as they relate to winning overrides vs not. Take this one, for ex
https://github.com/Mutagen-Modding/Mutagen.Bethesda.Analyzers/blob/dev/Mutagen.Bethesda.Analyzers.Skyrim/Record/Cell/CellUnderscoreAnalyzer.cs
it's a problem if a cell's EDID has _
should that error remain in the readout if mods A, B, C all have an _ for a given cell, even though D has overridden it to not have one?
yes and no. The LO doesn't have the issue anymore, as the winning override has fixed it
buuut, A,B,C mods DO have an issue, technically, that could be improved
I think there will be different users that only care about their actual LO's result and if their game is stable
and then there will be users that want to know that A, B, C could be improved, so they can report them to the mod devs

---

Is that controlled by config? Eg, "hide if error is not on winning override"?
is that config per record? Or a more global one?

[ProfessionalDragonslayer]

I think hiding errors from non winning overrides should be the default behavior.

• A normal mod user only cares about the state of their LO and not how the underlying plugins look like.
• Mod authors will probably run an analyzer on a limited LO, with only plugin they are working on plus its masters in the first place.
• People working a big collaborative mod projects where people work on plugins that get merged into a master file would constantly see errors that are already fixed in their current plugin. Currently, the workflow is excluding all master files of the current plugin so that we only get the relevant topics.

I admit, that I am biased as contributor to multiple big mod projects but I think analyzing a whole load order for stuff that gets later overwritten is an edge case that won't come up very often.