Tim Condon
Tim Condon
I'm going to defer to @gwynne here as this kind of change is probably out of scope for Fluent 4 (though there very well may a way to do this...
Ping @gwynne this should work right? If the results get chunked we don't fetch stuff correctly
cc @gwynne
@gwynne I'm pretty sure this came from you originally 😆
Just an FYI, you can do ```swift return map(to: V.self, futureT, futureS) { t, s in return /// } ```
Migrating to FluentKit since Fluent is in the docs (as it's the Vapor integration part)
@lmcd No I don't think it is. The property wrappers require the enclosing type to be a `Model` to make all the syntactic sugar work and there's not really a...
You can't require property wrappers on properties in a protocol so there's no way for us to achieve this unfortunately
Will close this out, feel free to reopen if you have any other suggestions