Should have been done when web cookies were migrated to redux, but I haven't noticed this code then. Now that cookies are in redux on all platforms we can merge these two functions.
Details
Details
Tested that web app still works fine (logging in, out, navigation, sending messages). It's hard to test the of cookie change restarts the websocket because web can't really recover from cookies changes and it just causes a logout.
Diff Detail
Diff Detail
- Repository
- rCOMM Comm
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
lib/selectors/socket-selectors.js | ||
---|---|---|
37–42 ↗ | (On Diff #34525) | This behavior wasn't present on the web and now we're introducing it. Is it a good idea to do so? |
lib/selectors/socket-selectors.js | ||
---|---|---|
37–42 ↗ | (On Diff #34525) | I can't think of a situation where we wouldn't want this behaviour. If the cookie changes we should update the websocket connection so everything is in sync. Now that cookies on web are in redux we should try and treat it uniformly. |