Hello, my name is Tibor Blenessy and I work at SonarSource on JS/TS analysis for SonarQube/SonarCloud/SonarLint.
Our analyzer is based on ESLint and for some rules, we want to pass additional locations in the analyzed code which are relevant to the reported problem (e.g. we have rule which reports on dead-store and we want to highlight both where value is assigned and where the variable is declared). We then have a UI that uses this information and presents it either via the web interface or in the IDE. Currently, we did this in a bit hacky way by (ab)using message in the descriptor and passing JSON encoded object in it. This is problematic and hard to maintain. I was wondering if there is a better way to do this, or if ESLint would be open to extending the API in a way that would allow passing additional data from the rule? Thank you for your time. Best regards Tibor Blenessy -- You received this message because you are subscribed to the Google Groups "ESLint" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/eslint/da6c9c13-9fed-4177-99a9-642c83f4d61en%40googlegroups.com.
