Explore >> Select a destination
|
You are here 
|
blog.metaobject.com | ||
| | | | |
williamboles.com
|
|
| | | | | Dealing with a JSON network response in iOS projects used to be a pain - you would have to manually parse the response, extract the required values, ignore those that weren't needed, and build your model instances ??. Then came along `Codable` and all that changed. | |
| | | | |
benoitpasquier.com
|
|
| | | | | It's been almost two years that Combine has been introduced to the Apple developer community. As many developer, you want to migrate your codebase to it. You don't want to be left behind but you're not sure where to start, maybe not sure if you want to jump to SwiftUI either. Nothing to worry, let's see step by step how to migrate an iOS sample app using UIKit and RxSwift to Combine. | |
| | | | |
atomicbird.com
|
|
| | | | | In a previous post I wrote about How JSON compares to Apple property lists and the obstacles to converting data between them. That was a while ago but the post is still accurate, as far as it goes. But Swift changes the situation in some ways, so an update is in order. Recap: JSON vs. Property Lists The previous post was motivated by the problems some people encountered trying to download JSON from a server and then save it as a property list. | |
| | | | |
aarol.dev
|
|
| | | Anyone who has implemented a simple HTTP 1.1 server can tell you that it is a really simple protocol. Basically, it's a text file that has some specific ... | ||
