You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The logic is that when you type functions you are providing predicates for the banned function warning. However, you aren't enabling the banned function warning, just configuring it. So separately you ignored it, and haven't put in a corresponding unignore directive, so it remains ignored. Does that at least make sense why it happens that way?
Yeah, that makes sense. Is there a way to enable them after configuring them?
It seems like in the more normal configuration (not ignoring everything), enabling and configuring go hand in hand. But when using ignore: {}, these become separate steps. That makes sense of #747 as well, the difference there being that I figured out a workaround for that.
In HLint 2.2.2, the following config:
causes no warning to be issued on the following module:
whereas the appropriate warnings are raised without the
ignore: {}
. This is counterintuitive to me, because the README says:The text was updated successfully, but these errors were encountered: