NodeAlgo : Fix plug presets inheritance #5799
Merged
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.
By getting the first output plug with presets, as opposed to just the first output plug, as this was causing incorrect inheritance on plugs with multiple outputs.
Internally at IE this came up when we had a plug that had been promoted, and then was being used in a couple of Expressions. In this case an Expression plug was being checked for presets as it came first in the outputs list.
Checklist