You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe. ProfilePage, ProfileHeader, Comment, Post and every component that's associated to the authenticated user is also associated to the guest ( for example another user in the app ).
Now the problem is that when you open the profile page of somebody else it first shows your data and then switches to his/her data when it arrives and that's not how I want it to work. So maybe we can have a HOC Route which sends the user to 2 different layouts ( one with the authenticated user, and another for the other user ) which means that we will have 2 versions of components for each feature. I'm not really sure if this is ideal to do, so I will label this issue as a question. Let me know if there are better ways of handling authUser/urlUser ( other users ) in the app.
Also it would be perfect if we can combine profileRoute & privateRoute because they both contain duplicated data ( subscriptions ) and they are almost identical.
You can work on this feature by creating and using a branch called feature/fix-routes
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
ProfilePage, ProfileHeader, Comment, Post
and every component that's associated to the authenticated user is also associated to the guest ( for example another user in the app ).You can work on this feature by creating and using a branch called
feature/fix-routes
The text was updated successfully, but these errors were encountered: