Fixes Function and LambdaFunction classes to push active function instance names #374
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.
Description
Closes #364
This PR resolves an issue with how function names are set when invoking the
AIQContext.push_active_function
from theFunction
andLambdaFunction
classes. Now,instance_name
is passed into theLambdaFunction.from_info
factory method and is an argument in class instance construction. This change removes ambiguity when working withIntermediateStep
objects and exported traces when the same function is configured >1 times in the configuration object.By Submitting this PR I confirm: