How to disable Sensor ESLint-based SonarJS?












0















In our environment we already use ESLint to produce json report. Starting from Sonarqube 7.2, SonarJS plugin can import this report file.



But I see in analysis report that some Sensor ESLint-based SonarJS also starting. But this one does not understand our React based project sysntax, and trying to do dual work, actualy
Is there any way to disable this sensor?










share|improve this question



























    0















    In our environment we already use ESLint to produce json report. Starting from Sonarqube 7.2, SonarJS plugin can import this report file.



    But I see in analysis report that some Sensor ESLint-based SonarJS also starting. But this one does not understand our React based project sysntax, and trying to do dual work, actualy
    Is there any way to disable this sensor?










    share|improve this question

























      0












      0








      0








      In our environment we already use ESLint to produce json report. Starting from Sonarqube 7.2, SonarJS plugin can import this report file.



      But I see in analysis report that some Sensor ESLint-based SonarJS also starting. But this one does not understand our React based project sysntax, and trying to do dual work, actualy
      Is there any way to disable this sensor?










      share|improve this question














      In our environment we already use ESLint to produce json report. Starting from Sonarqube 7.2, SonarJS plugin can import this report file.



      But I see in analysis report that some Sensor ESLint-based SonarJS also starting. But this one does not understand our React based project sysntax, and trying to do dual work, actualy
      Is there any way to disable this sensor?







      sonarqube eslint sonarjs






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 13 '18 at 18:34









      Sergejs DegtjarsSergejs Degtjars

      11




      11
























          1 Answer
          1






          active

          oldest

          votes


















          0














          You should not disable this sensor. Currently SonarJS is gradually migrated from its own parser to espree (ESLint parser). Sensor ESLint-based SonarJS runs rules on espree-compalible AST. Currently it's only small subset of rules, but in future entire SonarJS functionality (rules, metrics, highlighting) will be based on it. Sensor ESLint-based SonarJS doesn't rely on your eslint configuration, currently it executes only rules activated in SonarQube and having eslint-based implementation.



          The right action to make is to report to SonarJS team the problem you have with parsing you React project code.






          share|improve this answer























            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53287466%2fhow-to-disable-sensor-eslint-based-sonarjs%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            You should not disable this sensor. Currently SonarJS is gradually migrated from its own parser to espree (ESLint parser). Sensor ESLint-based SonarJS runs rules on espree-compalible AST. Currently it's only small subset of rules, but in future entire SonarJS functionality (rules, metrics, highlighting) will be based on it. Sensor ESLint-based SonarJS doesn't rely on your eslint configuration, currently it executes only rules activated in SonarQube and having eslint-based implementation.



            The right action to make is to report to SonarJS team the problem you have with parsing you React project code.






            share|improve this answer




























              0














              You should not disable this sensor. Currently SonarJS is gradually migrated from its own parser to espree (ESLint parser). Sensor ESLint-based SonarJS runs rules on espree-compalible AST. Currently it's only small subset of rules, but in future entire SonarJS functionality (rules, metrics, highlighting) will be based on it. Sensor ESLint-based SonarJS doesn't rely on your eslint configuration, currently it executes only rules activated in SonarQube and having eslint-based implementation.



              The right action to make is to report to SonarJS team the problem you have with parsing you React project code.






              share|improve this answer


























                0












                0








                0







                You should not disable this sensor. Currently SonarJS is gradually migrated from its own parser to espree (ESLint parser). Sensor ESLint-based SonarJS runs rules on espree-compalible AST. Currently it's only small subset of rules, but in future entire SonarJS functionality (rules, metrics, highlighting) will be based on it. Sensor ESLint-based SonarJS doesn't rely on your eslint configuration, currently it executes only rules activated in SonarQube and having eslint-based implementation.



                The right action to make is to report to SonarJS team the problem you have with parsing you React project code.






                share|improve this answer













                You should not disable this sensor. Currently SonarJS is gradually migrated from its own parser to espree (ESLint parser). Sensor ESLint-based SonarJS runs rules on espree-compalible AST. Currently it's only small subset of rules, but in future entire SonarJS functionality (rules, metrics, highlighting) will be based on it. Sensor ESLint-based SonarJS doesn't rely on your eslint configuration, currently it executes only rules activated in SonarQube and having eslint-based implementation.



                The right action to make is to report to SonarJS team the problem you have with parsing you React project code.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 19 '18 at 8:58









                Elena VilchikElena Vilchik

                854511




                854511






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53287466%2fhow-to-disable-sensor-eslint-based-sonarjs%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Florida Star v. B. J. F.

                    Error while running script in elastic search , gateway timeout

                    Adding quotations to stringified JSON object values