{"action":"opened","issue":{"url":"https://api.github.com/repos/yargalot/grunt-accessibility/issues/44","repository_url":"https://api.github.com/repos/yargalot/grunt-accessibility","labels_url":"https://api.github.com/repos/yargalot/grunt-accessibility/issues/44/labels{/name}","comments_url":"https://api.github.com/repos/yargalot/grunt-accessibility/issues/44/comments","events_url":"https://api.github.com/repos/yargalot/grunt-accessibility/issues/44/events","html_url":"https://github.com/yargalot/grunt-accessibility/issues/44","id":327199057,"number":44,"title":"Allow forcing the accessibility task to succeed and let Grunt continue","user":{"login":"prantlf","id":733193,"avatar_url":"https://avatars0.githubusercontent.com/u/733193?v=4","gravatar_id":"","url":"https://api.github.com/users/prantlf","html_url":"https://github.com/prantlf","followers_url":"https://api.github.com/users/prantlf/followers","following_url":"https://api.github.com/users/prantlf/following{/other_user}","gists_url":"https://api.github.com/users/prantlf/gists{/gist_id}","starred_url":"https://api.github.com/users/prantlf/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/prantlf/subscriptions","organizations_url":"https://api.github.com/users/prantlf/orgs","repos_url":"https://api.github.com/users/prantlf/repos","events_url":"https://api.github.com/users/prantlf/events{/privacy}","received_events_url":"https://api.github.com/users/prantlf/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-05-29T07:26:15Z","updated_at":"2018-05-29T07:26:15Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"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.\r\n\r\nFor 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:\r\n\r\n```js\r\n  accessibility: {\r\n    'full-report': {\r\n      options: {\r\n        force: true, // ignores the error and lets Grunt continue\r\n        reportType: 'json',\r\n        reportLocation: 'pending'\r\n      },\r\n      src: ['**/*.html']\r\n    },\r\n    'check-fixed': {\r\n      src: ['**/*.html']\r\n    }\r\n  }\r\n```\r\n\r\nused in this task:\r\n\r\n```js\r\n  grunt.registerTask('test', [\r\n    'continue:on', 'accessibility:report-all', 'continue:off',\r\n    'accessibility:check-fixed'\r\n  ]);\r\n```\r\n\r\nWhat do you think about adding the `force` option?"}}
{"actor":{"display_login":"prantlf"}}