-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix types for validateInput hook arguments on update operations #8819
Conversation
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit d622b0d:
|
1c8d944
to
e26a754
Compare
Thanks @acburdine! |
@@ -106,9 +131,14 @@ export const lists: Lists = { | |||
return resolvedData; | |||
}, | |||
}, | |||
validateInput: ({ context, inputData, addValidationError }) => { | |||
validateInput: ({ context, operation, inputData, addValidationError }) => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My intent is to replace this soon with per operation typed equivalent, equivalent to validate.create
, validate.update
and validate.delete
, or similar. Like we have with resolveInput
.
Or at least validateInput.create
and validateInput.update
for now.
9cd03d6
to
d622b0d
Compare
looks like these were updated incorrectly in #8808. Checked the other types and these appeared to be the only incorrect ones.
didn't create an issue/repro case since it seems to be a pretty straightforward bug/typo, though if I need to create an issue/repro let me know and I can do that 😄 I did vet out this change in my project via patch-package.