Support Fluent API in read operations #36
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #12 with the solution approach described in #12 (comment). I further productionized it to make sure it handled arrays correctly, and added some tests to make sure of that fact.
This, of course, is a workaround at best and a terrible hack at worst. That said, the lack of support for Fluent API is significantly hampering adoption of client extensions, and this behavior is backed with an integration test, so we will get warning if Prisma Client breaks this behavior. I would much prefer resolution of prisma/prisma#24653 in the long term.