Oddbean new post about | logout
▲ ▼
ca5d9187 | 1 years ago (raw) | root | parent | reply | flag 
 @810ec5be nice! Will look at this a bit more closely over the weekend but those rules reflect my own experience. The devil is in the details 😂 I also love how you used a map wrapper as an example. It’s such a great illustration of the problems one often runs into.
▲ ▼
Chris Eidhof | 1 years ago (raw) | root | parent | reply | flag 
 @dbc45806 thanks! Let me know if you find anything missing/wrong.
▲ ▼
ca5d9187 | 1 years ago (raw) | root | parent | reply | flag 
 @810ec5be Hey Chris, I'll probably have a long tail of questions/comments as I get back into the project that's using UIView views heavily... Here's the first ;)

Background question: what is the lifecycle of the coordinator? I always thought it was essentially tied to the life of the UIView, but I can't seem to confirm this with docs now that I check.

This is an interesting question because your example code sets `.parent` in `updateUIView` as if the coordinator may have changed...
▲ ▼
Chris Eidhof | 1 years ago (raw) | root | parent | reply | flag 
 @dbc45806 the lifecycle of the coordinator is tied to the lifecycle of the swiftui view (and so is the uiview). Setting parent copies all the properties from the swiftui view to the coordinator, as these might have changed.