That's interesting your point about useEffect. I mean I am using it because I'm using the functional way to build things vs. class. I'd prefer the class way hon

That's interesting your point about useEffect. I mean I am using it because I'm using the functional way to build things vs. class. I'd prefer the class way honestly so I can just use the regular lifecycles eg. didMount/willMount/etc... I did figure out how to fix the issues eg. prop depedency, but it is kind of annoying when anything inside the useEffect triggers the warnings. Most recently I had a mobile app I had to make and it had a navbar/body/bottom navbar. I built the app split in three, so the navbar/bottom navbar took the routes to render what is shown, similar to the body... but this caused communication issues eg. you click on a thing in the bottom navbar, affects something in body and something renders/updates in the top navbar too. yeah my architecting can use work I don't deny that. Generally though it's the whole "action causes re-render" that I'm not 100% with but again probably goes back to architecture.