refactor(client): internally split client into separate sync / async classes #876
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
RobertCraigie
force-pushed
the
refactor/client
branch
from
55fea85
to
01e24f6
Compare
RobertCraigie
force-pushed
the
refactor/client
branch
4 times, most recently
from
0a55c62
to
949b77c
Compare
RobertCraigie
force-pushed
the
refactor/client
branch
from
0f35274
to
47f6447
Compare
RobertCraigie
force-pushed
the
refactor/client
branch
from
47f6447
to
9c0c508
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
More laying of the ground work for #871. This doesn't quite fully support using separate sync / async classes yet as we still only generate a single
Prismaclass with all the model actions on it, but this gets us much closer to that point :)Note:
prisma.buildertoprisma._builder, constructor now requiresprisma_modelsandrelational_field_mappingsarguments