Enable IFunctionExecutor in InvocationFeatures #3200
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
surgupta-msft
approved these changes
Oct 17, 2025
kshyju
reviewed
Oct 17, 2025
kshyju
approved these changes
Oct 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Issue describing the changes in this PR
resolves #1666
Pull request checklist
release_notes.mdAdditional information
This PR allows for an
IFunctionExecutorimplementation to be supplied on a per-invocation bases via invocation features. That feature will not be set by default. When it is not present, the existing behavior remains of using the DI registeredIFunctionExecutor. This allows for extensions to selective override the execution behavior of specific invocations.