JakubMisek haskellmcravin1, you probably have a settings.json or .editorconfig that overrides the problem's severity. Examples can be found at https://docs.devsense.com/vscode/problems/suppressing-diagnostics/ Please let me know if that was the case.
haskellmcravin1 How am I to globally have the warning while suppressing the specific scoped known non-problem code? The child declares its own property. and the parent references it with static::
JakubMisek haskellmcravin1, the warning can be forced using .editorconfig as shown below: [*.php] php_diagnostic = warning Please check if you don't have warnings overriden in your .editorconfig More details can be found at https://docs.devsense.com/vscode/problems/suppressing-diagnostics/#editorconfig
haskellmcravin1 Yes, it is set in .editorconfig... I want to override it locally. Is that not possible?
JakubMisek haskellmcravin1, currently, the .editorconfig forces it (but I agree we should respect the @suppress tag). In this case, you can comment it out from .editorconfig since warning is the default value anyways.
