[io-managers-deps] Properly handle deps mapping in multi_asset decorator #26466
+66
−11
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.
Summary & Motivation
Properly handle deps in the multi_asset decorator. Previously, the behavior when various combinations of multi_asset deps-related args were smashed together was not really under test.
Now that build_and_validate_named_ins can handle overlaps in deps and ins, we can simplify the logic in this part of the decorator significantly. Still leaving a hefty comment about why we disallow unmapped inputs _outside_of build_and_validate_named_ins.
How I Tested These Changes
I added a bunch of new test cases for all the possible interactions.