4 ms·

> React assumes that if you call useState many times, you do it in the same order during every render. Note they also say: > We provide a linter plugin to enf

> React assumes that if you call useState many times, you do it in the same order during every render. Note they also say: > We provide a linter plugin to enforce these rules automatically. Makes me feel a little better.

maaaats 8y ago
Why couldn't one just pass in `this` to useState, a key, or something similar? Like, if I have two state variables, pass in a name for both, instead of relying on the order being the same.
- needz 8y ago
  It's meant for functional components, not classes.
  - Touche 8y ago
    This doesn't answer the question.
  - maaaats 8y ago
    "This" existed in javascript long before classes. No idea why my relevant question is down voted.
    - kiliancs 8y ago
      Not in arrow functions, which are very common and any solution should certainly contemplate them.
    - kaoD 8y ago
      "this" isn't bound in functional components because there's nothing to bind it to.
- zwily 8y ago
  And what would `this` be in that function?
adriancooney 8y ago
I doubt the linter will enforce the same-ordering, that would require state between runs. I think the linter just ensures hooks are run at the top level in the functional component.
- atomwaffel 8y ago
  And it wouldn't need to. You're free to move around calls to useState() to your heart's content in your code, you just need to call them in the same order during the lifecycle of your component.