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
My team would like to fail our builds depending on linting output, which is impossible to do without parsing the output from the linting tasks (yagni, bikeshed, etc).
It would be helpful to allow the option to raise an exception or, perhaps better yet, expose the problems found as Clojure data structures so that a wrapper task could fail drastically when problems occur.
As it is we are having to dissect and reimplement portions of the library to get the desired behavior (or parse the output as strings).
The text was updated successfully, but these errors were encountered:
Thanks! Next time I'm getting my hands dirty with this I can try it out. Seems close-able for now, but will let you close the issue. Thanks again for the quick response.
My team would like to fail our builds depending on linting output, which is impossible to do without parsing the output from the linting tasks (yagni, bikeshed, etc).
It would be helpful to allow the option to raise an exception or, perhaps better yet, expose the problems found as Clojure data structures so that a wrapper task could fail drastically when problems occur.
As it is we are having to dissect and reimplement portions of the library to get the desired behavior (or parse the output as strings).
The text was updated successfully, but these errors were encountered: