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
Right now a Map is used to store all data since it is more performant and this simplifies updating data. However, this isn't feasible for storing server data right now as it is rather large as seen in the screenshot below:
This should instead be stored as nested arrays since they will be ordered properly and don't need indexPathString which is rather large to tack on to the data. In general, this probably warrants proper serialize/deserialize utilities.
The text was updated successfully, but these errors were encountered:
Thinking through this more, only the computed data should be stored since that's the only thing server renders care about and will be even better for performance ✨
Right now a Map is used to store all data since it is more performant and this simplifies updating data. However, this isn't feasible for storing server data right now as it is rather large as seen in the screenshot below:
This should instead be stored as nested arrays since they will be ordered properly and don't need
indexPathString
which is rather large to tack on to the data. In general, this probably warrants proper serialize/deserialize utilities.The text was updated successfully, but these errors were encountered: