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.
this makes it so that if we have 2 create or edit actions, they work
we still need a lot of work to support other types e.g. add/remove edges
still need better default behavior when all 3 custom fields aren't provided
still need better to fix inconsistency in naming conventions of input names e.g. default is
CreateUserAction
for action name butUserCreateInput
for input names. The latter is fine for graphql but dubious for entsAlso, this stems from inconsistency in default behavior e.g.
CreateUserAction
and 'userCreate`