https://linear.app/comm/issue/ENG-245/make-sure-state-sync-mechanism-works-after-client-id-migration
There was bug in the id schema conversion during the state check. The async function returned by the getClientResponsesSelector modified the arguments gotten from the input selectors. That meant if the async function was called multiple times (and redux state didn't change so it wasn't regenerated) it would try to convert the already converted state. This diff moves the conversion outside of the async function so it's done only once.
Details
Details
- Reviewers
kamil tomek - Commits
- rCOMMbc4f14cb5e95: [lib] Fix state check with new ID schema
Check that if the state sync runs for the second time without redux changes no errors are thrown. (that was what was triggering the errors without this diff)
Diff Detail
Diff Detail
- Repository
- rCOMM Comm
- Lint
Lint Not Applicable - Unit
Tests Not Applicable