It's an exercise, for me, myself, I alone, to see which I prefer among #React state management architecture patterns - lifting state up or plumbing in #Redux. With the help of some nifty conditional rendering here, my #choros home page component either displays hardcoded songs (this was a requirement so the app could run during Mass with choristers' devices switched to airplane mode), or custom songs chosen from the search form component. But to make this work, re-using the same (dumb) table component, I have had to do a bit of prop drilling. And that's with only TWO state "little trees" - songs and custom songs. Much as I deplore the extra complexity of Redux, even with #RTK, in a training context, I have commented in the search component that :
// when prop drilling is a solution, redux becomes an option...