Closed bejitono closed 2 years ago
Do we need the Alamofire dependency? Alamofire is only included temporary with the idea it would be removed when Nathan's Swift code is updated. I don't think we want to add more code that's dependent on Alamofire.
Do we need the Alamofire dependency? Alamofire is only included temporary with the idea it would be removed when Nathan's Swift code is updated. I don't think we want to add more code that's dependent on Alamofire.
Yeah agreed. I'll remove it.
@ronaldmannak I think the current base client only handles rpc requests, so I went ahead and implemented a separate REST-based client. Is that ok for you?
Yes, that sounds like a great idea.
I believe ObjC.io has a useful async/await version of their minimalistic and generic networking client. It might be useful to check it out.
Nice, objc.io is great resource! Did you mean this library: https://github.com/objcio/tiny-networking. It also has an async/await extension.
The link you posted was relating to async URLSession delegates which would be great for download tasks, which we don't need (yet).
This PR implements an etherscan client to fetch contract details (contract name and ABI) to be able to parse transaction inputs and provide more useful information (e.g. contract invocations and params).