Why is SwiftUI so broken and not improving layered UI functionality

Question

Created 1w

Replies 1

Boosts 0

Participants 2

Again and and again, I reach the point in a new application where I need to make structural changes in components and my data model, and the SwiftUI compiler fails to compile and just reports "I'm lost in the weeds", with no indication of what it was last working on, aside from a particular level in a multi-layered nested UI.

This typically happens when a sub-views construction is not coded correctly because I changed that view and am looking for what broke, by just letting the compiler tell me what is not compatible. This is how refactoring has been done for ages and it's just amazingly frustrating that Apple engineers don't seem to understand nor care about this issue enough to fix it.

Why does this problem persist through version after version of SwiftUI? Is no-one actually using it for anything?

Boost

Answer 1

darkpaw OP

1w

What do you mean by:

SwiftUI compiler fails to compile and just reports "I'm lost in the weeds", with no indication of what it was last working on, aside from a particular level in a multi-layered nested UI.

Have you raised any bugs about it? Perhaps if you explain - in a bug - exactly what the issue is, Apple's developers might be able to make improvements.

I raised a bug where I'd renamed a binding variable but forgotten to rename it in one place it was being used, and the compiler said it was unable to compile. Apple's developers fixed it, so when I forget to rename the use of the variable now it fails at that point, so I know where the issue is.

If you do the same, these bugs will be fixed. You'll be happier, other developers will be happier, Apple developers will be happier. It's the right thing to do :)

0