Change Details

Part of [ENG-4959](https://linear.app/comm/issue/ENG-4959) Suggested in D9255, which was a previous attempy at storing hashes in redux We want to store thread hashes in redux so that we don't have to calculate all of them whenever the state check is triggered. Instead we keep them in sync using thread ops. Additionaly the hashes will be now generated based on the client schema so we convert them on the server instead of the client.

Part of [ENG-4959](https://linear.app/comm/issue/ENG-4959) Suggested in D9255, which was a previous attempt at storing hashes in redux We want to store thread hashes in redux so that we don't have to calculate all of them whenever the state check is triggered. Instead we keep them in sync using thread ops. Additionally the hashes will be now generated based on the client schema so we convert them on the server instead of the client. On login/register/web page load instead of handling all of the thread updates at once we convert them in batches of 50, one every 0.5s.

Part of [ENG-4959](https://linear.app/comm/issue/ENG-4959) Suggested in D9255, which was a previous attempyt at storing hashes in redux We want to store thread hashes in redux so that we don't have to calculate all of them whenever the state check is triggered. Instead we keep them in sync using thread ops. Additionally the hashes will be now generated based on the client schema so we convert them on the server instead of the client. On login/register/web page load instead of handling all of the thread updates at once we convert them in batches of 50, one every 0.5s.