Array prototype is read only, properties should not be added no-extend-native












3














So basically I have this code:



Array.prototype.inState = function (needle, haystack) {
let index = this.findIndex(value => value[needle] === haystack);

return index === -1;
};


and it works fairly enough to check if the given needle is exists in the react state or not. but ESlint keep saying that:



Array prototype is read only, properties should not be added  no-extend-native


so my question is: What is wrong with my code ?










share|improve this question



























    3














    So basically I have this code:



    Array.prototype.inState = function (needle, haystack) {
    let index = this.findIndex(value => value[needle] === haystack);

    return index === -1;
    };


    and it works fairly enough to check if the given needle is exists in the react state or not. but ESlint keep saying that:



    Array prototype is read only, properties should not be added  no-extend-native


    so my question is: What is wrong with my code ?










    share|improve this question

























      3












      3








      3







      So basically I have this code:



      Array.prototype.inState = function (needle, haystack) {
      let index = this.findIndex(value => value[needle] === haystack);

      return index === -1;
      };


      and it works fairly enough to check if the given needle is exists in the react state or not. but ESlint keep saying that:



      Array prototype is read only, properties should not be added  no-extend-native


      so my question is: What is wrong with my code ?










      share|improve this question













      So basically I have this code:



      Array.prototype.inState = function (needle, haystack) {
      let index = this.findIndex(value => value[needle] === haystack);

      return index === -1;
      };


      and it works fairly enough to check if the given needle is exists in the react state or not. but ESlint keep saying that:



      Array prototype is read only, properties should not be added  no-extend-native


      so my question is: What is wrong with my code ?







      javascript reactjs eslint






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 20 at 7:02









      AH.Pooladvand

      37010




      37010
























          1 Answer
          1






          active

          oldest

          votes


















          1














          From EsLint Docs:




          In JavaScript, you can extend any object, including builtin or
          “native” objects. Sometimes people change the behavior of these native
          objects in ways that break the assumptions made about them in other
          parts of the code.



          For example here we are overriding a builtin method that will then
          affect all Objects, even other builtin.




          // seems harmless
          Object.prototype.extra = 55;

          // loop through some userIds
          var users = {
          "123": "Stan",
          "456": "David"
          };

          // not what you'd expect
          for (var id in users) {
          console.log(id); // "123", "456", "extra"
          }


          In-short, Array.prototype.inState will extend the array.prototype and hence whenever you want to use an array, the instate function will be added to that array too.



          So, in your case this example will be applied to array.






          Array.prototype.inState = function (needle, haystack) {
          let index = this.findIndex(value => value[needle] === haystack);

          return index === -1;
          };


          // loop through some userIds
          var users = [{"123": "Stan"},{"456": "David"}];

          // not what you'd expect
          for (var id in users) {
          console.log(users[id]); // "123", "456", "extra"
          }





          WorkAround





          You can add this line to ignore warning.



          /*eslint no-extend-native: ["error", { "exceptions": ["Object"] }]*/ to ignore that warning.


          Ref: https://eslint.org/docs/rules/no-extend-native






          share|improve this answer























          • @AH.Pooladvand this would be a good conversion developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/…
            – Just code
            Nov 20 at 7:54











          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%2f53387813%2farray-prototype-is-read-only-properties-should-not-be-added-no-extend-native%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









          1














          From EsLint Docs:




          In JavaScript, you can extend any object, including builtin or
          “native” objects. Sometimes people change the behavior of these native
          objects in ways that break the assumptions made about them in other
          parts of the code.



          For example here we are overriding a builtin method that will then
          affect all Objects, even other builtin.




          // seems harmless
          Object.prototype.extra = 55;

          // loop through some userIds
          var users = {
          "123": "Stan",
          "456": "David"
          };

          // not what you'd expect
          for (var id in users) {
          console.log(id); // "123", "456", "extra"
          }


          In-short, Array.prototype.inState will extend the array.prototype and hence whenever you want to use an array, the instate function will be added to that array too.



          So, in your case this example will be applied to array.






          Array.prototype.inState = function (needle, haystack) {
          let index = this.findIndex(value => value[needle] === haystack);

          return index === -1;
          };


          // loop through some userIds
          var users = [{"123": "Stan"},{"456": "David"}];

          // not what you'd expect
          for (var id in users) {
          console.log(users[id]); // "123", "456", "extra"
          }





          WorkAround





          You can add this line to ignore warning.



          /*eslint no-extend-native: ["error", { "exceptions": ["Object"] }]*/ to ignore that warning.


          Ref: https://eslint.org/docs/rules/no-extend-native






          share|improve this answer























          • @AH.Pooladvand this would be a good conversion developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/…
            – Just code
            Nov 20 at 7:54
















          1














          From EsLint Docs:




          In JavaScript, you can extend any object, including builtin or
          “native” objects. Sometimes people change the behavior of these native
          objects in ways that break the assumptions made about them in other
          parts of the code.



          For example here we are overriding a builtin method that will then
          affect all Objects, even other builtin.




          // seems harmless
          Object.prototype.extra = 55;

          // loop through some userIds
          var users = {
          "123": "Stan",
          "456": "David"
          };

          // not what you'd expect
          for (var id in users) {
          console.log(id); // "123", "456", "extra"
          }


          In-short, Array.prototype.inState will extend the array.prototype and hence whenever you want to use an array, the instate function will be added to that array too.



          So, in your case this example will be applied to array.






          Array.prototype.inState = function (needle, haystack) {
          let index = this.findIndex(value => value[needle] === haystack);

          return index === -1;
          };


          // loop through some userIds
          var users = [{"123": "Stan"},{"456": "David"}];

          // not what you'd expect
          for (var id in users) {
          console.log(users[id]); // "123", "456", "extra"
          }





          WorkAround





          You can add this line to ignore warning.



          /*eslint no-extend-native: ["error", { "exceptions": ["Object"] }]*/ to ignore that warning.


          Ref: https://eslint.org/docs/rules/no-extend-native






          share|improve this answer























          • @AH.Pooladvand this would be a good conversion developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/…
            – Just code
            Nov 20 at 7:54














          1












          1








          1






          From EsLint Docs:




          In JavaScript, you can extend any object, including builtin or
          “native” objects. Sometimes people change the behavior of these native
          objects in ways that break the assumptions made about them in other
          parts of the code.



          For example here we are overriding a builtin method that will then
          affect all Objects, even other builtin.




          // seems harmless
          Object.prototype.extra = 55;

          // loop through some userIds
          var users = {
          "123": "Stan",
          "456": "David"
          };

          // not what you'd expect
          for (var id in users) {
          console.log(id); // "123", "456", "extra"
          }


          In-short, Array.prototype.inState will extend the array.prototype and hence whenever you want to use an array, the instate function will be added to that array too.



          So, in your case this example will be applied to array.






          Array.prototype.inState = function (needle, haystack) {
          let index = this.findIndex(value => value[needle] === haystack);

          return index === -1;
          };


          // loop through some userIds
          var users = [{"123": "Stan"},{"456": "David"}];

          // not what you'd expect
          for (var id in users) {
          console.log(users[id]); // "123", "456", "extra"
          }





          WorkAround





          You can add this line to ignore warning.



          /*eslint no-extend-native: ["error", { "exceptions": ["Object"] }]*/ to ignore that warning.


          Ref: https://eslint.org/docs/rules/no-extend-native






          share|improve this answer














          From EsLint Docs:




          In JavaScript, you can extend any object, including builtin or
          “native” objects. Sometimes people change the behavior of these native
          objects in ways that break the assumptions made about them in other
          parts of the code.



          For example here we are overriding a builtin method that will then
          affect all Objects, even other builtin.




          // seems harmless
          Object.prototype.extra = 55;

          // loop through some userIds
          var users = {
          "123": "Stan",
          "456": "David"
          };

          // not what you'd expect
          for (var id in users) {
          console.log(id); // "123", "456", "extra"
          }


          In-short, Array.prototype.inState will extend the array.prototype and hence whenever you want to use an array, the instate function will be added to that array too.



          So, in your case this example will be applied to array.






          Array.prototype.inState = function (needle, haystack) {
          let index = this.findIndex(value => value[needle] === haystack);

          return index === -1;
          };


          // loop through some userIds
          var users = [{"123": "Stan"},{"456": "David"}];

          // not what you'd expect
          for (var id in users) {
          console.log(users[id]); // "123", "456", "extra"
          }





          WorkAround





          You can add this line to ignore warning.



          /*eslint no-extend-native: ["error", { "exceptions": ["Object"] }]*/ to ignore that warning.


          Ref: https://eslint.org/docs/rules/no-extend-native






          Array.prototype.inState = function (needle, haystack) {
          let index = this.findIndex(value => value[needle] === haystack);

          return index === -1;
          };


          // loop through some userIds
          var users = [{"123": "Stan"},{"456": "David"}];

          // not what you'd expect
          for (var id in users) {
          console.log(users[id]); // "123", "456", "extra"
          }





          Array.prototype.inState = function (needle, haystack) {
          let index = this.findIndex(value => value[needle] === haystack);

          return index === -1;
          };


          // loop through some userIds
          var users = [{"123": "Stan"},{"456": "David"}];

          // not what you'd expect
          for (var id in users) {
          console.log(users[id]); // "123", "456", "extra"
          }






          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Nov 20 at 7:14

























          answered Nov 20 at 7:08









          Just code

          7,96642966




          7,96642966












          • @AH.Pooladvand this would be a good conversion developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/…
            – Just code
            Nov 20 at 7:54


















          • @AH.Pooladvand this would be a good conversion developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/…
            – Just code
            Nov 20 at 7:54
















          @AH.Pooladvand this would be a good conversion developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/…
          – Just code
          Nov 20 at 7:54




          @AH.Pooladvand this would be a good conversion developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/…
          – Just code
          Nov 20 at 7:54


















          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.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • 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%2f53387813%2farray-prototype-is-read-only-properties-should-not-be-added-no-extend-native%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

          Ottavio Pratesi

          Tricia Helfer

          15 giugno