Sharing-friendly response in App state
Closed this issue · 0 comments
mejedi commented
At the moment, response is massaged prior to being installed as state.response
. It complicates sharing. There's little sense in sharing a massaged response. The transformation speeds up rendering by avoiding pointless re-computation; however in future App versions we are likely to enhance the transformation causing compatibility issues.
Store the response as-is and use memoization whenever processing is necessary prior to rendering a response.