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 Grunt command-line option --force can suppress the failure in any task. However, sometimes it is needed to suppress the failure in just one task and check the result of the other as usual. Tasks usually support their own boolean option force for this.
For example, one instance f the accessibility task could be forced to generate a full report including problems, which have not been fixed yet, while another one could perform the hard check. For example, like this configuration:
accessibility: {'full-report': {options: {force: true,// ignores the error and lets Grunt continuereportType: 'json',reportLocation: 'pending'},src: ['**/*.html']},'check-fixed': {src: ['**/*.html']}}
If the Grunt task should not fail, it must not call grunt.fail.warn, but grunt.log.warn instead. What do you think about supporting the force option like that?
The text was updated successfully, but these errors were encountered:
The Grunt command-line option
--force
can suppress the failure in any task. However, sometimes it is needed to suppress the failure in just one task and check the result of the other as usual. Tasks usually support their own boolean optionforce
for this.For example, one instance f the
accessibility
task could be forced to generate a full report including problems, which have not been fixed yet, while another one could perform the hard check. For example, like this configuration:used in this task:
If the Grunt task should not fail, it must not call
grunt.fail.warn
, butgrunt.log.warn
instead. What do you think about supporting theforce
option like that?The text was updated successfully, but these errors were encountered: