Change Details

This diff handles moving all of the deep link handling logic into the one. The main thing here is we use both parse methods (`parseSecretFromInviteLinkURL` and `parseKeysFromQRCodeURL`) on the current link, and then handle what to do based on whether the regex finds a match. We check for the invite link first because it is possible in theory for there to be an invite link like `/invite/qr-code/` if the community is called `qr-code`, but it's not really possible for the QR code link to contain an `invite` route. Depends on D9027 Part of [[ https://linear.app/comm/issue/ENG-4810/combine-deep-link-handlers-listeners-into-one-component | ENG-4810 ]]

This diff handles moving all of the deep link handling logic into the one. The main thing here is we use both parse methods (`parseSecretFromInviteLinkURL` and `parseKeysFromQRCodeURL`) on the current link, and then handle what to do based on whether the regex finds a match. We check for the invite link first because it is possible in theory for there to be an invite link like `/invite/qr-code/` if the community is called `qr-code`, but it's not really possible for the QR code link to contain an `invite` route. Depends on D9027 Part of [[ https://linear.app/comm/issue/ENG-4810/combine-deep-link-handlers-listeners-into-one-component | ENG-4810 ]]

This diff handles moving all of the deep link handling logic into the one. The main thing here is we use both parse methods (`parseSecretFromInviteLinkURL` and `parseKeysFromQRCodeURL`) on the the current link, and then handle what to do based on whether the regex finds a match. We check for the invite link first because it is possible in theory for there to be an invite link like `/invite/qr-code/` if the community is called `qr-code`, but it's not really possible for the QR code link to contain an `invite` route. Depends on D9027 Part of [[ https://linear.app/comm/issue/ENG-4810/combine-deep-link-handlers-listeners-into-one-component | ENG-4810 ]]