Redundant useEffect Dependency in Header Component

[Amansingh0807]

The Header component has redundant useEffect blocks that both fetch userInfo from localStorage and dispatch the setUserInfo action. This results in multiple dispatches of setUserInfo whenever the auth state changes, potentially causing unintended updates to the auth state.

Solution:
Remove the useEffect that has auth as a dependency, keeping only the one that runs on the initial mount to load userInfo from localStorage.

[arunkumar413]

@Amansingh0807 Actually the header should re-render on on the auth change (such as login and logout) as well that's why I added the effect with dependency. Also sometimes the users directly visit a URL or reload the URL in such cases also the the effect should run and header should re-render.

[Amansingh0807]

Actually the header should re-render on on the auth change (such as login and logout) as well that's why I added the effect with dependency. Also sometimes the users directly visit a URL or reload the URL in such cases also the the effect should run and header should re-render.

Thank you for the clarification! I now understand the purpose of having the auth as a dependency in the useEffect. It ensures the header re-renders appropriately on login, logout, and page reload, which is crucial for keeping the UI in sync. I'll revise my PR accordingly. Thank you for your feedback!