-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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 task processing input validation #46058
Conversation
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.
🙈 I recently discovered that I've been using the + operator wrong
cbfad3f
to
0593fbf
Compare
0593fbf
to
b5b6a72
Compare
b5b6a72
to
79164fb
Compare
Signed-off-by: Julien Veyssier <julien-nc@posteo.net>
79164fb
to
7e1dd0b
Compare
… input/output keys that are not in the task values Signed-off-by: Julien Veyssier <julien-nc@posteo.net>
@marcelklehr I had to adjust again to make the tests pass. As the purpose of this method is to remove keys, this fix seems fine to me. But do we actually check that all the input shape fields are defined in the task? If not, do you think it should be done? |
Yes, the validateInput and validateOutput methods check this |
It was dropping some optional inputs.