title: Are methods with a "method could be static" warning considered bad form in JavaScript/TypeScript?
body: <p>I have noticed that if I write a method that only acts on local variables of calling methods (does not directly interact with a class variable) then I get a warning that the method can be static.</p>
  
  <p>Sometimes it's nice to abstract a large piece of code into a separate method. Is this somehow consider bad practice in JavaScript/TypeScript? </p>
  
  <p>Since I keep getting these warnings I'm taking a chance that the post police will pounce on me for asking a question that could invite opinions. Let me defend against that by saying that the warnings I'm getting are not opinions. They are definite warnings. That suggests that there exists an answer that is not opinion, at least from the perspective of the people who decided to create those warnings.  </p>
  
  <p>EDIT: 
  I was asked to put code here to provide a valid reason as to why I would want to do this. I personally don't think this adds any clarity to question I asked but here's an example of a method that was producing the warning in WebStorm.</p>
  
  <pre><code>//Change object array in *.content objects to values array
  //noinspection JSMethodCanBeStatic
  transformData(visibleData) {
      const ret: any = {};
      ret.headings = visibleData.headings;
      ret.checkbox = this.checkBox;                                                   //add if the table needs checkboxes
      ret.content = [];
      for (let i = 0; i &lt; visibleData.content.length; i++) {
          ret.content.push(_.values(visibleData.content[i]));
      }
      return ret;
  }
  </code></pre>
  
  <p>The point of this function is to take a clone of the instance, so as not to modify the instance itself, and create a different object, mainly a values only array, which will be used to databind in the template. I did this so my table template could be reusable since columns vary in number.</p>