Federation branch - Modified templates to check for updateMany; added federation prefix from paljs/generator; updated paljs/generator package #26
Conversation
This file contains hidden or 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
…ctive to global gql. Added ERD generator and chance.js for random seeding
Author
|
For reference, this resolves #10 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
As per title.
Paljs/generator's
generator.run()now returns the entire dmmf document. You might find that useful for getting the model names, I also added a bunch of useful maps as type extensions. These include federation related fields for model fields,generateUpdateManyfor models which return a boolean value whether or not a model should generate anupdateManymutation or not.updateManyshould not be generated if a model contains only unique fields or relations; there would be no valid arguments as in order for updateMany to work you would have to update a single value over multiple instances of the object which is impossible if all the fields are unique. Therefore Prisma itself will not generate any args for the updateMany, which caused a compile error in the original paljs/Generator. I have fixed this issue in my fork, and updated the templates in this pull request accordingly.