Web3Wallet implementation + integration tests

[alexander-lsvk]

Description

Web3Wallet proxy implementation according to the interface described here

• Breaking change
• Requires a documentation update

[flypaper0]

@llbartekll as I remember we found the way how to avoid force casts for pairing client. Or we decided to leave it like that?

[llbartekll]

We have fixed it for Networking having two vars: instance and interactor I think we could do the same with pairing

[flypaper0]

also need to remove all packages imports from all files

[flypaper0]

Cocoapods putting all sources in single framework, so it doesn't know what is Auth, WalletConnectSign etc

Need to remove all

import WalletConnectSign
import Auth

And imports should be

@_exported import Auth
@_exported import WalletConnectSign

Agree it looks like a little wired but supporting both SPM and Cocoapods is a kind of pain

[alexander-lsvk]

@llbartekll @flypaper0 I added unit tests for Web3Wallet in the last commit. It required adding abstraction levels for Auth, Sign and Pair -> AuthClientProtocol, SignClientProtocol, PairClientProtocol.

I'm not really satisfied with this *Protocol suffix, I'd be more pleased to have protocol named, i.e. SignClient, and then SignClientMock and SignClient*Something* for implementation. But the question is what this Something should be 🤔

Any suggestions?

[llbartekll]

Looks good to me.

[flypaper0]

@llbartekll @flypaper0 I added unit tests for Web3Wallet in the last commit. It required adding abstraction levels for Auth, Sign and Pair -> AuthClientProtocol, SignClientProtocol, PairClientProtocol.

I'm not really satisfied with this *Protocol suffix, I'd be more pleased to have protocol named, i.e. SignClient, and then SignClientMock and SignClient*Something* for implementation. But the question is what this Something should be 🤔

Any suggestions?

For me all namings is good, but it must be consistant across project and all our sdk's

[flypaper0]

lgtm!