Hacker News Reader

> 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.

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.

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.

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.

It's meant for functional components, not classes.

This doesn't answer the question.

"This" existed in javascript long before classes. No idea why my relevant question is down voted.

Not in arrow functions, which are very common and any solution should certainly contemplate them.

"this" isn't bound in functional components because there's nothing to bind it to.

And what would `this` be in that function?

Reply on news.ycombinator.com