In the Ventura SDK, SwiftUI gained a new public struct named Group. As a result, when a file imports both Fluent and SwiftUI and attempts to use Fluent's @Group in a Model, the compiler prefers the SwiftUI definition over the Fluent-provided typealias, despite ample syntactic clues as to which is intended.
Ideally, we would figure out a means to hint to the compiler how to disambiguate without requiring awkward syntax like @FluentKit.GroupProperty<Self, ...>; failing that, try to find a way to at least get the compiler to show a less misleading error message. (Currently the error claims that "Content" cannot be inferred - since Content is a Vapor protocol, this only further obscures the actual problem.)
[!NOTE]
This is the same kind of name collision as seen in #588. Swift 5.9 seems to be more prone to such collisions than previous versions, as these seem to have been rarely, if ever, encountered in the past despite both collisions having existed for some time.
In the Ventura SDK, SwiftUI gained a new public struct named
Group. As a result, when a file imports bothFluentandSwiftUIand attempts to use Fluent's@Groupin aModel, the compiler prefers the SwiftUI definition over the Fluent-providedtypealias, despite ample syntactic clues as to which is intended.Ideally, we would figure out a means to hint to the compiler how to disambiguate without requiring awkward syntax like
@FluentKit.GroupProperty<Self, ...>; failing that, try to find a way to at least get the compiler to show a less misleading error message. (Currently the error claims that "Content" cannot be inferred - sinceContentis a Vapor protocol, this only further obscures the actual problem.)