ahaha to always stay on top, don't miss the next talks that will be out from Swift Heroes 2024. keep an eye on the 2025 site because tickets are coming out at a special price only for this week: swiftheroes.com/2025/ ,🚀
Thank you for this video, and thank you ( the speaker ) for taking the time and effort to make the presentation. This is definitely a real problem with SwitftUI to make non trivial view and view components. Would be nice to get a tutorial with source code examples..
the goal of Swift Heroes is exactly this, help you to discover new techniques to better manage your work. 🚀 And developers like you who have learned them through experience, explain them to you 👨🏻💻
The ViewWapper idea you have is not necessary. You can still return concrete type from view extension, remember SwiftUI view is a struct. Just assign the self instance to another variable of the same type of the View and return that. You have just returned a copy of the View no need to wrap a copy of view in another View Wrapper. You are now free to set properties on that new instance as your not mutating the original instance which the extension function was called on. Structs are assign by value not pass by reference. In view wrapper original property it should be named copy as that view is actually a copy of the original. Otherwise thanks for the info you presented, well done.
That was very informative. Also props to her for giving a talk not in her native language, she did amazing.
absolutely, congratulations to Gyuree 👏🏻
I'm definitely guilty for using many parameters in my views. Thanks for sharing your recipe for success :) Cheers 🍻
ahaha to always stay on top, don't miss the next talks that will be out from Swift Heroes 2024.
keep an eye on the 2025 site because tickets are coming out at a special price only for this week:
swiftheroes.com/2025/ ,🚀
Very informative! Please upload more such talks. Thank you 😊
ahaha, we are working on it, every week 2 or more talks from 2024 will be out 🛠
@@SwiftHeroes Awesome, looking forward to them!
What an amazing talk. Thank you so much :)
Glad it was helpful! 🚀
Thank you for this video, and thank you ( the speaker ) for taking the time and effort to make the presentation. This is definitely a real problem with SwitftUI to make non trivial view and view components. Would be nice to get a tutorial with source code examples..
Don't miss the next talks... 😊
Really helpful, I always wanted to avoid too many parameters in reusable components.
good job 🥂
This is really interesting, I have been using environments mostly but this looks nicer
the goal of Swift Heroes is exactly this, help you to discover new techniques to better manage your work. 🚀
And developers like you who have learned them through experience, explain them to you 👨🏻💻
재밋게 봤어요
감사합니다
thank you
You're welcome 🤗
The ViewWapper idea you have is not necessary. You can still return concrete type from view extension, remember SwiftUI view is a struct. Just assign the self instance to another variable of the same type of the View and return that. You have just returned a copy of the View no need to wrap a copy of view in another View Wrapper. You are now free to set properties on that new instance as your not mutating the original instance which the extension function was called on. Structs are assign by value not pass by reference. In view wrapper original property it should be named copy as that view is actually a copy of the original. Otherwise thanks for the info you presented, well done.
thanks for the feedback, it will be useful to the whole community 🙌🏼