id summary reporter owner description type status component version severity resolution keywords cc stage has_patch needs_docs needs_tests needs_better_patch easy ui_ux 26472 Allow finer granularity in the ability to silence checks Peter Zsoldos Adam Johnson "==== Proposal ==== Add an optional kwarg to modelfields called `silenced_system_check=`, which would default to `None` or an empty collection As `CheckMessage` already has access to the object it applies to, it should be a matter of adding an extra check in `is_silenced` to check whether the warning id is present in the global system settings or inside the modelfield's own silenced system checks https://github.com/django/django/blob/master/django/core/checks/messages.py#L54 ==== Context ==== on a large application that was recently upgraded to 1.8, we wanted to add a step to the build to fail is `manage.py check` would report any warnings. However, there are many uses of `models.ForeignKey(unique=True)`, and thus upgrading all of them right now is not feasible. The only option we have is to use `settings.SILENCED_SYSTEM_CHECKS`, however, that silencing the warning there would apply to any new models/fields that are added, for which we would actually be happy to fail the build." New feature assigned Core (System checks) dev Normal Accepted 1 0 0 1 0 0