Thanks for the very useful explanation. I've watched the video a few months ago and didn't understand the advantages of Combine. But now everything makes perfectly sense!
Hi Brain Advent great video on combine framework where even apple docs are cumbersome about combine but you explained clearly about the necessity of framework. Can you do more videos on combine that includes debounce clasess.
very good video.I guess tutorials should be that simple and concise as you have used UIKit for your demo.Create other videos with UIKit as most of developers not switched to SwiftUI
Update for the sink modifier: add receive completion parameter if compiler is showing error ---> "Referencing instance method 'sink(receiveValue:)' on 'Publisher' requires the types" 👌🏾 .sink(receiveCompletion: { _ in print("process complete") }, receiveValue: { value in print("A summer day of \(value) Celcius") })
Trial-and-error showed the original code worked by changing let weatherPublisher = PassthroughSubject() into let weatherPublisher = PassthroughSubject() but I'm not wise enough to know if this is a good idea.
Have problems following your code Referencing instance method 'sink(receiveValue:)' on 'Publisher' requires the types 'Publishers.Filter.Failure' (aka 'WeatherError') and 'Never' be equivalent
I saw this same error on my code when I ran it and changed it to the alternate: let weatherPublisher = PassThroughSubject() ...which worked, but see comments below for a better solution.
Thank you for this tutorial. But : are you sure a publisher can have only one subscriber ? Cuz i tested with multiple subscribers and it seams working fine. with both sink and assign.
Lemme ask maybe a kinda odd question. Why would you do this? When you could simply do sendButton.isEnabled.toggle() in the IBAction of the switch. I understand your demonstrating Combine. I get that. And maybe that is the answer, but. Beyond that, and making this a bit more real. What is the benefit of it in this case. Over doing just the one line of toggle?
I too was asking myself the same question. For such a simple use-case, you wouldn't normally do this. This form of declarative programming is only useful if you know you're working on a view that has several states defined by more than one input. In that case, Combine would be great - it'd figure out how to render your view rather than you having to trust your own brain capacity to account for each case.
Nice, but this is something we could have done with a property observer and Notification Center observer. Is it just because the task demonstrated here was too simple to warrant the Combine framework, or is there more to it than just this?
It was just an example. Combine shows its power when you need to use operators and different types of subscribers to, well, "combine" streams. e.g. setting a Label based on many different, asynchronous inputs. Such as in a Login screen, or as a result of multiple network operations.
A lot of companies still require iOS 12, and will do so for a few more years. For that, they need RxSwift. But yes, for greenfield projects, Combine is the way to go.
Dear friend, i need to know how to make Xcode accept more than 10 toggles per page, as when i want to add more than 10 toggle it won't allow? i need also to know how to make toggle label clickable and shows a pop up window to write inside it, is that possible ?
I'm sure you've found an answer within the last 8 months, but a SwiftUI view only allows a max of 10 subviews. You can use Group {} to get around that. With 10 Groups of 10 Toggles each, you could easily have 100 toggles in a page.
Apparently no one knows how to create a list with dynamic sections And delete rows functionality. Like a list of employees sectioned by departments and still can delete rows!! Can you?!
![[LIVE] : ONE ลุมพินี 82 วันนี้!! คู่เอก | ยอดไอคิว vs อับดัลลาห์](http://i.ytimg.com/vi/hSsyTl_9bqs/mqdefault.jpg)
This is phenomenally well explained 👌
I'm just now getting started with combine and reactive programming. This is a great way to get my feet wet. Thanks.
Thanks for the very useful explanation. I've watched the video a few months ago and didn't understand the advantages of Combine. But now everything makes perfectly sense!
I don’t even use UIKit and I understood it clearly. Awesome tutorial.
beautiful explanation , thanks 👍
I have never put nutmeg into mashed potatoes. I will try it next time.
Most important lesson learned from this video
😂
Came here for Combine. Stayed for the cooking tips.
Awesome video for quick understanding.
you making such a great video can you make it more for combine framework.
High quality video and high quality teaching! Thank you so much :)
Hi Brain Advent great video on combine framework where even apple docs are cumbersome about combine but you explained clearly about the necessity of framework. Can you do more videos on combine that includes debounce clasess.
very good video.I guess tutorials should be that simple and concise as you have used UIKit for your demo.Create other videos with UIKit as most of developers not switched to SwiftUI
Awesome introduction, you helped me a lot!! thanks!!!
Update for the sink modifier:
add receive completion parameter if compiler is showing error ---> "Referencing instance method 'sink(receiveValue:)' on 'Publisher' requires the types" 👌🏾
.sink(receiveCompletion: { _ in print("process complete") }, receiveValue: { value in
print("A summer day of \(value) Celcius")
})
Thanks Man, finally it works after i add receivecompletion
Trial-and-error showed the original code worked by changing let weatherPublisher = PassthroughSubject() into let weatherPublisher = PassthroughSubject() but I'm not wise enough to know if this is a good idea.
Excellent example! A bit confusing though! I thought Subscribers had to be reference types.
Super decent tutorial with plenty of graphics.
Thank you very much for Amazing lesson
Super simple explanation! Really nice tutorial 👏
Have problems following your code
Referencing instance method 'sink(receiveValue:)' on 'Publisher' requires the types 'Publishers.Filter.Failure' (aka 'WeatherError') and 'Never' be equivalent
I saw this same error on my code when I ran it and changed it to the alternate:
let weatherPublisher = PassThroughSubject()
...which worked, but see comments below for a better solution.
Thank you for this tutorial.
But : are you sure a publisher can have only one subscriber ?
Cuz i tested with multiple subscribers and it seams working fine. with both sink and assign.
Yeah I thought that too!
Great video! Thanks
Lemme ask maybe a kinda odd question. Why would you do this? When you could simply do sendButton.isEnabled.toggle() in the IBAction of the switch. I understand your demonstrating Combine. I get that. And maybe that is the answer, but. Beyond that, and making this a bit more real. What is the benefit of it in this case. Over doing just the one line of toggle?
I think it's just a matter of programming style. Using combine is some kinda of declarative, however, your style is imperative.
I too was asking myself the same question. For such a simple use-case, you wouldn't normally do this. This form of declarative programming is only useful if you know you're working on a view that has several states defined by more than one input. In that case, Combine would be great - it'd figure out how to render your view rather than you having to trust your own brain capacity to account for each case.
still very helpful video in 2023
thanks! i was looking for this
Great explanation!
Xcode 11 beta 7: .sink is only available when Failure is Never
@DRCT, that error means that the 1st closure in Sink(receiveCompletion:) is not implemented.
Thanks so much!
Thanks Brian, where can I get source code?
Nice, but this is something we could have done with a property observer and Notification Center observer. Is it just because the task demonstrated here was too simple to warrant the Combine framework, or is there more to it than just this?
It was just an example. Combine shows its power when you need to use operators and different types of subscribers to, well, "combine" streams. e.g. setting a Label based on many different, asynchronous inputs. Such as in a Login screen, or as a result of multiple network operations.
IT seems that RxSwft will be deprecated soon with this Combine framework.
A lot of companies still require iOS 12, and will do so for a few more years. For that, they need RxSwift. But yes, for greenfield projects, Combine is the way to go.
Can you please add space after the variable name?
Great tutorial! good job
Could you share me this slide, Brian? Thanks a lot
Thank you 👍
How I can import SwiftUI in SceneKit/SpriteKit? Like a collectionView as SwiftUI
Dear friend, i need to know how to make Xcode accept more than 10 toggles per page, as when i want to add more than 10 toggle it won't allow? i need also to know how to make toggle label clickable and shows a pop up window to write inside it, is that possible ?
I'm sure you've found an answer within the last 8 months, but a SwiftUI view only allows a max of 10 subviews. You can use Group {} to get around that. With 10 Groups of 10 Toggles each, you could easily have 100 toggles in a page.
example with uikit begin at 11:40
Hi Brian! What is messageLabel??
UILabel
Apparently no one knows how to create a list with dynamic sections And delete rows functionality. Like a list of employees sectioned by departments and still can delete rows!!
Can you?!
If I recall correctly, Apple showed something like that in Diffable Data Sources session. You should check that out. That doesn't use Combine though.
The question is irrelevant to the video. It's just an attempt to grab free tech help.
The way you did it is poor, because you would have to create a message publisher for each property on the message object.
Do you have a video showing how to do it better?
Really hard to follow after you switched to the actual project.
👌👌👌
Thanks for the tutorial. 18:55 hope we can unsubscribe later!
Nutmeg in mashed potatoes? Thats new.
Could you check your emails :)
That's not new at all :-)