Silent warnings

Background

Add project configuration silent-warnings to silence warnings which are configurable.

Task description

• Add project configuration item
• Validate no overlap between fatal and silent warnings

silent-warnings:
- overlaps

Acceptance Criteria

Configurable warnings can be silenced on a project by project basis.

changed the description

Was this feature proposed anywhere ?

Is it just an assumption that since we have fatal warnings, we must want to silence them also ?

I don't think I agree with this feature, for instance; the overlap warnings have an explicit feature for whitelisting specific files such that they are not considered overlaps; a blanket statement to silence this warning would not necessarily be a good thing.

No proposal has been done formally for this, it was created out of a thought during !700 (merged), in which two CoreWarnings were added. I can imagine that we may want to produce some warnings which certain projects may choose to silence.

E.g. A warning suggesting that aliases are used throughout projects.

This feature not desired but just a thought in the back of my head during other work.

added Wontfix label

Let's close this.

closed