Inertia.js how to prevent component destroy
Hello, Im stuck trying to make twitter-like app. I have a feed with infinite-scroll but when I open a post or author profile and then navigating back, the feed component re-renders. I reached the saving of posts-array state to not lose "loaded-more" parts and I can set the same scroll position but it does not look as good as twitter works.
If you check twitter you will see how great it handles navigation through menu or page history with saving states like they are keeping alive. Please help me to reach same level of usability.
Also I have noticed that my app starts to lag after multiple opening posts and going back. What could be the problem? (To save posts and scroll position I router.remember() them before destroy).
Thank you in advance.
Please or to participate in this conversation.