If I get you right, you mean a different container for every segment, so you don't mix up different contexts, correct? I do that for really big components or when I need to fetch stuff separately or just make a reusable block of code for multiple pages. Otherwise, I just stick to something similar to what I did above.
Software Engineering Manager and Endurance Running Race Director - Have lots of ideas of how to simplify and automate endurance race management through workflow optimization and software development.
If I get you right, you mean a different container for every segment, so you don't mix up different contexts, correct? I do that for really big components or when I need to fetch stuff separately or just make a reusable block of code for multiple pages. Otherwise, I just stick to something similar to what I did above.
Cool....Yup. Separation of concerns and isolating functionality to its own container that you can just pass around and use wherever.