Okay nice, thank you!
Yeah, I use the value in a lot of deeply nested places, and it usually isn’t even just one value, but a set of filterModel, sortModel and paginationModel that are always used together but need their separate states. Directly passing those through parameters even just one or two levels down really messes with the readability the code. But yeah, if it’s just one-off states only used in one child I do pass them as regular parameters :)
Neat, thanks! I do use useContext, as far as I know the previous way to do it was to wrap children in a specific Context Consumer tag? Never quite understood the syntax of the old method haha