I'm working on a linter, but right now, elm-format is your best bet for maintaining code format. We use this with the `--validate` flag to ensure that all checked in code matches elm-format.
On Fri, Dec 16, 2016 at 5:58 PM, Gian Giacomo Ermacora <giangiacomo.ermac...@gmail.com> wrote: > Hello everybody, > > my team and I are working on a complex project using Elm (today it was > upgraded to version 0.18). > Usually we run static source analysis using SonarQube and I am wondering if > there is some way or an existing plugin for that tool to support the Elm > source code > > Any suggestions? I can also accept to use another tool for the static > analysis, it is not a problem, the required scenario is that Jenkins must be > able to call this external tool that must do every night its task > > Thank you everybody in advance for suggestions and for this space. > > My best regards, > > Gian. > > -- > You received this message because you are subscribed to the Google Groups > "Elm Discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to elm-discuss+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to elm-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
