Understanding Swift KeyPaths

[@TuanHoang-qj3yq]

Thank you for your dedication to providing excellent content with great clarity. I still have not clearly seen the benefit of keyPath. I have tried to use “dot notation” approach to the two practical examples and achieved the same results as with keyPath’s approach. I am sure that it is powerful but with my current limited knowledge unfortunately, I have not been able to appreciate the significant benefits of keyPath yet. 😢 I hope I soon will.

[@CarterTsai-p5t]

The content is always great as usual. Thank you for all your work and sharing these.

[@bonnydonny]

Very helpful, thanks.

[@StewartLynch]

Thank. Glad to offer some insights.

[@andresraigoza2082]

Great examples, thank you so much for your work 🙂

[@parietal100]

Great video. Learned some new techniques. Thank you.

[@hunterdobb]

Awesome! Love the format of these videos! Thank you 😊

[@StewartLynch]

Glad you enjoy them

[@chesterman18g]

great video Stewart!

[@robertdavis7262]

Thanks again! I've needed this one (and one on subscripts, so ditto on the request for that) for a long time.

[@robertdavis7262]

BTW, I had the same issue showing the view in the playground.

[@andrejkling3886]

Thanks a lot for SwiftUI’s examples 💫 please keep them up 🎈

[@femialiu]

Thanks a lot Mr Stewart! This series is really helpful. Any chance you'd cover Swift subscripts in one of the videos? I actually requested you cover Swift KeyPaths when you asked on Twitter, so thanks for this!

[@StewartLynch]

That sounds like a good topic. I will check it out.

[@femialiu]

@@StewartLynch Thanks.

[@gakkieNL]

Great series Stewart!

[@vatanachhorn9534]

Thank you!

[@StewartLynch]

You're welcome!

[@РоманРоман-н4н]

wow, such a great job, thanks! looks like way safer js))))

[@wallacewittkoff8123]

An extremely useful video. Thanks to it I (and some of your other videos, ie CoreData) I was able to figure out and now share a use case for key paths. Suppose you want a picker that will then display one total for any number of parameters in a CoreData entity. Populating an array with a struct that included a name and a keypath of type “ReferenceWritableKeyPath did the job. The structure name is used for the picker and the tag links it to variable that is used for the reducing function (in my case a static function locate in the core data properties extension. Keypaths add a whole new dimension to data manipulation where parameters can now be treated as data as well. Perhaps there is another way to do this as well. I did try use an enum and associated value constructor and a static var all cases but this did not work for me.

[@StewartLynch]

Thanks for sharing

[@cestlacroix]

Great!!!!!

[@kadeus]

Great as always my question do u have any database course Tutorial to buy or watch? Thx sir

[@StewartLynch]

I have a series on using Realm, kzbin.info/aero/PLBn01m5Vbs4B8xgS_iEEuJtM_3BuZ7fiV and another that uses Core Data and it starts here kzbin.info/www/bejne/pZiUg2l-fr6Ia8U

[@kadeus]

@@StewartLynch thx 🙏🏼

[@AllanSpreys]

Would you recommend Core Data or Realm for a new project Stewart?

[@StewartLynch]

I would recommend Core Data and I would also recommend Mark Moeykens book on Core Data. www.bigmountainstudio.com/core-data/77jt8

[@AllanSpreys]

@@StewartLynch thank you!

[@victorriurean]

nice

[@jidhabraham3383]

same

[@shurale85]

Great content except example of wine.. as for me