| 1 | | ELS diagnostics |
| | 1 | == Erlang LS diagnostics == |
| | 2 | |
| | 3 | RefactorErl now can integrate its diagnostics into Erlang LS. To following page will help you with the setup and give you some feature highlight. |
| | 4 | |
| | 5 | |
| | 6 | == What you need == |
| | 7 | -[https://erlang-ls.github.io Erlang LS] version: **** |
| | 8 | - RefactorErl version: ***** |
| | 9 | |
| | 10 | |
| | 11 | == How to set it up == |
| | 12 | |
| | 13 | RefactorErl is like any other diagnostics in ELS, just it is computed outside of it. To enable you need to enable it in the config file of ELS. |
| | 14 | To learn more about how to config Erlang LS visit: [https://erlang-ls.github.io/configuration/ ELS Configuration] |
| | 15 | |
| | 16 | {{{ |
| | 17 | diagnostics: |
| | 18 | enabled: |
| | 19 | - refactorerl |
| | 20 | }}} |
| | 21 | |
| | 22 | Some extra configuration is needed as the diagnostics are computed on the RefactorErl node. |
| | 23 | You need to add a new root entry to diagnostic file, containing the node's name where RefactorErl is running. (you must start the tool in distributed mode) |
| | 24 | |
| | 25 | {{{ |
| | 26 | refactorerl: |
| | 27 | node: "nodeName@hostName" |
| | 28 | }}} |
| | 29 | |
| | 30 | Finally by default there are no diagnostics are run, even if the tool is enabled as a Erlang LS diagnostic. You need to enable certain diagnostics manually. |
| | 31 | |
| | 32 | |
| | 33 | |