We currently export the entire redux store in support logs. This includes the client which can become quite large in enterprise support logs. I saw a 200MB redux store today and it was 99% a massive client object. Something in the client (iterator of some sort or linked list) tracks the prev item and ends up with massively nested objects when trying to stringify
Something in client.configs has a deeply nested structure when stringifying
The client object probably isn't particularly useful in the support logs, so stop exporting it and only export the parts of the redux store which might be useful
LogExport.ts should probably have a blacklist of redux keys for the getReduxDataString function
We currently export the entire redux store in support logs. This includes the client which can become quite large in enterprise support logs. I saw a 200MB redux store today and it was 99% a massive client object. Something in the client (iterator of some sort or linked list) tracks the prev item and ends up with massively nested objects when trying to stringify
Something in client.configs has a deeply nested structure when stringifying
The client object probably isn't particularly useful in the support logs, so stop exporting it and only export the parts of the redux store which might be useful
LogExport.tsshould probably have a blacklist of redux keys for thegetReduxDataStringfunction