-
Notifications
You must be signed in to change notification settings - Fork 191
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Auth, Sign] #485 remove pairing #486
Conversation
import WalletConnectUtils | ||
import WalletConnectPairing | ||
|
||
class DeletePairingService { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we move it in WalletConnectPairing package?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh, I see. Whey using different NetworkInteractors..
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah exactly, even the protocol method is the same
if pairingStorage.hasPairing(forTopic: topic) { | ||
try await deletePairingService.delete(topic: topic) | ||
} else if sessionStorage.hasSession(forTopic: topic) { | ||
try await deleteSessionService.delete(topic: topic) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pairing and a session at the same time? I mean: do we need to clear pairing and session together on disconnect call?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if so, I think is better to have 1 DeleteSessionService, which clean pairing and session storage
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
one topic corresponds to one pairing or one session and we have a common public method for deletion.
So we either delete a pairing or a session.
…V2 into #447-remove-pairing # Conflicts: # Package.swift # Sources/Auth/Services/Common/NetworkingInteractor.swift # Sources/Chat/ChatClient.swift # Sources/Chat/ChatClientFactory.swift # Sources/Chat/ProtocolServices/Common/MessagingService.swift # Sources/Chat/ProtocolServices/Invitee/InvitationHandlingService.swift # Sources/Chat/ProtocolServices/Inviter/InviteService.swift # Sources/Chat/Types/Message.swift # Sources/WalletConnectNetworking/NetworkInteractor.swift # Sources/WalletConnectNetworking/NetworkingInteractor.swift # Sources/WalletConnectNetworking/RequestSubscriptionPayload.swift # Sources/WalletConnectNetworking/ResponseSubscriptionPayload.swift # Tests/TestingUtils/NetworkingInteractorMock.swift
Description
Resolves #485 #447
How Has This Been Tested?
Due Dilligence