Renaud Lienhart on Nostr: In order to progressively migrate our remaining UIViewControllers to SwiftUI, I've ...
In order to progressively migrate our remaining UIViewControllers to SwiftUI, I've gotten into the habit of subclassing UIHostingController in order to easily split responsibilities. So far so good.
Apple doesn't warn against subclassing, but I still have the feeling this is not kosher. Did anybody encounter issues with this approach?
Published at
2024-02-05 22:05:12Event JSON
{
"id": "7bd11758b4190dd413253de335f74ce311664d0b3706e411ceed671dce1453b3",
"pubkey": "6552b030630993816cdf6f739269ea133436428583489f64263394e2c307b260",
"created_at": 1707170712,
"kind": 1,
"tags": [
[
"proxy",
"https://mastodon.social/users/layoutSubviews/statuses/111881139803229957",
"activitypub"
]
],
"content": "In order to progressively migrate our remaining UIViewControllers to SwiftUI, I've gotten into the habit of subclassing UIHostingController in order to easily split responsibilities. So far so good.\nApple doesn't warn against subclassing, but I still have the feeling this is not kosher. Did anybody encounter issues with this approach?",
"sig": "5c0f6225380600ee4f83f46b6d52648ea041759821495572ae548ff5d33ecef57d776eca20defb8c03f31ae0fdcc9684cdaa73a4d0fdac594e0d6e01d9a7cac3"
}
