HomePhabricator
Diffusion Comm 31f3b9f2cdd2

[web] Stop setting CSAT on initial redux state action

Description

[web] Stop setting CSAT on initial redux state action

Summary:
issue: ENG-6919
From D9122 it looks like commServicesAccessToken: null is sent from the keyserver as a result of decoupling web app and keyserver data. And back when keyserver would send all state fields in initial redux state with web app, we were just using the default null. So it looks like it wasn't supposed to do anything, it's just the default.

But because we were sending commServicesAccessToken: null, and initial redux state is being spread in the reducer, the CSAT would get set to null when the app was reloaded.
We don't want to stop sending the value from the keyserver though, to not reintorduce ENG-6849

Test Plan: Tested that in multikeyserver setup, CSAT is no longer set ot null after app is reloaded

Reviewers: tomek, michal

Reviewed By: michal

Subscribers: ashoat

Differential Revision: https://phab.comm.dev/D11350

Details

Provenance
inkaAuthored on Mar 19 2024, 5:16 AM
Reviewer
michal
Differential Revision
D11350: [web] Stop setting CSAT on initial redux state action
Parents
rCOMMadb2fa281ce5: [lib] Expose isAuthorized property in Tunnelbroker context
Branches
Unknown
Tags
Unknown