Page MenuHomePhabricator

[web] Stop setting CSAT on initial redux state action
ClosedPublic

Authored by inka on Mar 19 2024, 5:28 AM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Nov 22, 9:21 PM
Unknown Object (File)
Fri, Nov 22, 9:03 PM
Unknown Object (File)
Fri, Nov 22, 4:53 PM
Unknown Object (File)
Thu, Nov 7, 8:43 PM
Unknown Object (File)
Oct 21 2024, 4:47 PM
Unknown Object (File)
Oct 20 2024, 10:32 PM
Unknown Object (File)
Oct 16 2024, 9:53 PM
Unknown Object (File)
Oct 16 2024, 9:53 PM
Subscribers

Details

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

Diff Detail

Repository
rCOMM Comm
Branch
inka/csat
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

inka requested review of this revision.Mar 19 2024, 5:48 AM

We don't want to stop sending the value from the keyserver though, to not reintorduce ENG-6849

I think we actually could stop sending the value from the keyserver. useGetInitialReduxState is only called when a new webapp is initialized. And at this point this will be a new webapp which can handle the lack of commServicesAccessToken in the payload.

This revision is now accepted and ready to land.Mar 19 2024, 7:26 AM

Stop sending commServicesAccessToken from keyserver