SebastianVerified account

Fn takes in React Hook configurations, and returns a (factory that creates a) component that calls those hooks, and saves the most recent set of values they've produced. Intermediate factory step so *some* hooks config values can easily change from component to component

Don’t want to be the Hooks Police but not having to write this kind of code is kind of the point of Hooks. They’re intended to be used with a very direct style and not much abstraction. What are you aiming for?

If it’s just tests then it’s not too bad. Although I’ve learned to avoid this code in tests too. Nobody will be hurt if test contains some repetitive boilerplate copypaste. Makes it easy to tweak and debug. Those line savings in tests are rarely worth it.https://twitter.com/AdamRackis/status/1128717697477427200 …

Absolutely, positively, only in tests. Disagree strongly on LoC savings in tests, though. ime I've found strong DRY in tests leads to a more robust test suite, ie, adding new tests for every ridiculous edge case is a *lot* easier, so folks are more likely to do it.

I guess it depends on your team habits. I don’t mind copy pasting a verbose but clear test and starting from there. In fact probably prefer it to test I don’t understand.