Open fhchina opened 3 years ago
Eureka offers a rich library of pre-built components to make forms. That's every bit as useful in SwiftUI as it is in UIKit.
My team uses Eureka because we don't have to build everything from scratch, and I'm sure there are hundreds of teams that use it for the same reason.
Eventually more teams will start building apps with SwiftUI, and they'll want to build forms, but not want to write hundreds of lines of code to implement fundamental software architecture ("forms").
Eureka does it out of the box. That's every bit as useful for SwiftUI as UIKit. Even if it ends up being a separate project, doing the migration work on Eureka will be FAR easier than building a new project from scratch.
I think Eureka for SwiftUI would be a separate project. SwiftUI has a syntax that is similar to Eureka, if you just want to populate tables/lists. We haven't looked into creating a SwiftUI version in depth. Let's keep this thread as a discussion on why/ why not it could make sense to create a SwiftUI version.