Submit Your Ideas

We want to hear from you - vote for the features and improvements you'd most like to see, or submit your own ideas if you don't find them already listed.

Circle should handle eslint warnings better

Currently they show up as errors and make it more difficult to see the actual problems. They don't fail the build but are mixed in the error reporting

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Aug 10 2018
  • Future consideration
  • Attach files
  • Admin
    Alexey Klochay commented
    05 Sep 13:28

    Thanks for your idea! How do you currently run eslint? Would it be possible to separate it out into its own build step so that the output doesn’t mix up with the rest? Are you reporting eslint errors via JUnit XML?

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    05 Sep 16:22

    Yes eslint is it's own step and we output the xml. The problem arises when you set something to warn rather than error. The basic use case being you want to deprecate something but you can't really do it all in one fell swoop. The warnings show up as red failures in the error reporting in circle though so the warn feature of eslint is pretty much useless for circle since it can generate so much noise.