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
{{ message }}
This repository has been archived by the owner on Sep 19, 2020. It is now read-only.
This triggers FC005. Rightly so, but in this one particular case, I actually like the additional verbosity. I don't want to disable FC005 entirely in this cookbook, as I do want to be notified about violations in other recipes (or even elsewhere in the file). So I'm proposing this syntax (inspired by rubocop's):
This would also help those of us who break the build on a foodcritic limit to mark issues that have an open foodcritic issue. The addition of an optional reason field would also allow us to explain why we're disabling a rule at that point. That would let us track back to the foodcritic issue and remove the disabling of the rule when it was fixed.
Given something like:
This triggers FC005. Rightly so, but in this one particular case, I actually like the additional verbosity. I don't want to disable FC005 entirely in this cookbook, as I do want to be notified about violations in other recipes (or even elsewhere in the file). So I'm proposing this syntax (inspired by rubocop's):
The text was updated successfully, but these errors were encountered: