help refactoring context with useEffect into layout `beforeload`?
I'm trying to integreate openauth into a router project, and have been at this on and off for a week or so now. i've come up with a solution, but it's suboptimal and involves setting/getting jotai stores outside of react which seems to be generally discouraged.
basically there's this example i'm trying to roughly port. some of the things tripping me up, but here's my thought process, and would be deeply grateful to any willing to give some thoughts
- there's a bunch of logic happening in a useEffect w/ no deps. this tells me that I would prefer to just pull this logic into a
- ok, i pull the logic out, but now i need to set some values which, in the example, are state values. i'm not in a component anymore so i need a solution here -> use context to communicate btwn route loader and context
- i wrap my whole tree in an auth context
- the beforeload is at my _root, so now it's higher in the tree than everything else. this means that the auth context provider renders beneath it. seems like this defeats the solution of pulling it into context. not to mention that
this is sort of where my brain starts go a million different ways and i don't have a good model of how to solve this. i'm just wondering, is there a pattern for doing this type of thing? i'm sorry if this is vague and confusing, i'm just looking for any thoughts on how someone would go about this. my current solution is really not something i'd like to use, so looking for the "proper" way to handle this.
basically there's this example i'm trying to roughly port. some of the things tripping me up, but here's my thought process, and would be deeply grateful to any willing to give some thoughts
- there's a bunch of logic happening in a useEffect w/ no deps. this tells me that I would prefer to just pull this logic into a
beforeload__root- ok, i pull the logic out, but now i need to set some values which, in the example, are state values. i'm not in a component anymore so i need a solution here -> use context to communicate btwn route loader and context
- i wrap my whole tree in an auth context
- the beforeload is at my _root, so now it's higher in the tree than everything else. this means that the auth context provider renders beneath it. seems like this defeats the solution of pulling it into context. not to mention that
this is sort of where my brain starts go a million different ways and i don't have a good model of how to solve this. i'm just wondering, is there a pattern for doing this type of thing? i'm sorry if this is vague and confusing, i'm just looking for any thoughts on how someone would go about this. my current solution is really not something i'd like to use, so looking for the "proper" way to handle this.
