State management without a library was pretty tough for me. It took a while for me to grasp the concept that the state only existed in the instance it was used, so refreshing or navigating to a new page lost or reset the state. I spent a bit trying to use it as an on the fly database before realizing its limitations.
There was never really a solve as much as there was gaining an understanding of it. Learning more about props helped too. With props you can take the state of one component, pass it to another- and now that state persists into the next area you need it to continue working.
This is all a very simplistic breakdown of everything so take the "explanations" with a grain of salt.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
State management without a library was pretty tough for me. It took a while for me to grasp the concept that the state only existed in the instance it was used, so refreshing or navigating to a new page lost or reset the state. I spent a bit trying to use it as an on the fly database before realizing its limitations.
There was never really a solve as much as there was gaining an understanding of it. Learning more about props helped too. With props you can take the state of one component, pass it to another- and now that state persists into the next area you need it to continue working.
This is all a very simplistic breakdown of everything so take the "explanations" with a grain of salt.