Change Details

issue: https://linear.app/comm/issue/ENG-5990/add-setconnectionissue-action In this stack I will be replacing logouts dispatched from the socket with seting this new `connectionIssue` filed. This is because we don't want to log the user out of the app if we can't connect to one keyserver. We also don't want to log the user out of this keyserver, because that would result in the client removing the keyserver from the store. Instead, we decided to store information about the problem that the client is having with communicating with the keyserver. See the discussion in [[ https://linear.app/comm/issue/ENG-5808/refactor-logout-action-usages-connection-issue#comment-710a3e90 | ENG-5808 ]] for more details. See [[ https://linear.app/comm/issue/ENG-5913/check-all-places-that-select-all-keyservers-from-keyserverstore#comment-451a9908 | ENG-5913 ]] for an explanation of why it takes those values.

issue: https://linear.app/comm/issue/ENG-5990/add-setconnectionissue-action In this stack I will be replacing logouts dispatched from the socket with seting this new `connectionIssue` filed. This is because we don't want to log the user out of the app if we can't connect to one keyserver. We also don't want to log the user out of this keyserver, because that would result in the client removing the keyserver from the store. Instead, we decided to store information about the problem that the client is having with communicating with the keyserver. See the discussion in [[ https://linear.app/comm/issue/ENG-5808/refactor-logout-action-usages-connection-issue#comment-710a3e90 | ENG-5808 ]] for more details. See [[ https://linear.app/comm/issue/ENG-5913/check-all-places-that-select-all-keyservers-from-keyserverstore#comment-451a9908 | ENG-5913 ]] for an explanation of why it takes those values.

issue: https://linear.app/comm/issue/ENG-5990/add-setconnectionissue-action In this stack I will be replacing logouts dispatched from the socket with seting this new `connectionIssue` filed. This is because we don't want to log the user out of the app if we can't connect to one keyserver. We also don't want to log the user out of this keyserver, because that would result in the client removing the keyserver from the store. Instead, we decided to store information about the problem that the client is having with communicating with the keyserver. See the discussion in [[ https://linear.app/comm/issue/ENG-5808/refactor-logout-action-usages-connection-issue#comment-710a3e90 | ENG-5808 ]] for more details. See [[ https://linear.app/comm/issue/ENG-5913/check-all-places-that-select-all-keyservers-from-keyserverstore#comment-451a9908 | ENG-5913 ]] for an explanation of why it takes those values.