SwiftyJSON VS RxSwift

I don’t think you are going to be able to use JSONDecoder to do what you are asking. I see the problem is that you need to create a struct that has all the property names (pokemon names) in it in order to use JSONDecoder (that’s a pain). You need to resort to “parsing” the JSON and constructing your own data model to satisfy your requirements. Something like this might help. https://github.com/SwiftyJSON/SwiftyJSON

Up until now, I've been using SwiftyJSON, although it appears to be unmaintained. Is there an equivalent alternative which functions similarly? Thanks in advance

SwiftyJSON - The better way to deal with JSON data in Swift. Language: Swift.

I second /u/daisnb that if possible, make sure the data is a consistent format and types, but if you’re unable to do that, I think SwiftyJSON can help, as it loosens the strict type requirement of Swift when handling JSON data

I use RxSwift/RxCocoa and The Binder Architecture. That way View Controllers always show the most recent data from the service.

RxSwift - Reactive Programming in Swift. Language: Swift.

I do this with RxSwift and my CLE library. Using those you can do something like this:

I've tried going to RxSwift's source and copying the RxSwift folder into my playground file's Source folder but no dice, it complains about a source file not being found. I tried flattening all the files into one folder and had the same problem.

We have defined what async code is, and two basic issues we could have when working with it: running tasks serially and in parallel. For running tasks in parallel we saw that DispatchGroup can be a simple solution for that. I will recommend using a library for this though. What I taught you here is basic async knowledge, but in real world scenarios, this won't be this straightforward, so using a battle tested library is always an advantage when working in production. I personally recommend using Apple's Combine if you can (it is supported in iOS 13 and above) or using RxSwift otherwise Finally, I can't finish this article without mentioning async-await. With async-await, probably all of this discussion will be a thing of the past. It lets us write async code that can be written like sync code. You can see the proposal (already implemented and that will be released in the next version of swift) here, and even try it in your code following a tutorial like this one.

I think this is the most important thing to understand with all your heart. All subjects, relays and operators might seem scary, especially with Rx-hermetic jargon. But simplifying it in your head to a simple collection will help you to understand all concepts easily. For me it was a sudden click. If you want to learn more, official docs are great source and emphasize this concept: https://github.com/ReactiveX/RxSwift/blob/main/Documentation/GettingStarted.md#observables-aka-sequences