Fix false indeterminate function warning #757
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.
Summary
Fixes a false indeterminate function warning when using edited inputs in step state.
We show this warning when finding a brand new step that the Executor doesn't yet know about. If we've found this and there's a difference between the number of steps we've previously found and the amount of steps the Executor has given us, we display the warning.
The value we used for these counts was the
fulfilled
boolean, which tracks whether a step will resolve or reject based on Executor state. This, however, doesn't account for known steps when the Executor provides aninput
instead.This PR adds a small
hasStepState
boolean to each found step, such that we know if the Executor has any knowledge of the step without scoping it down to just resolve/reject.Checklist
Added a docs PR that references this PRN/A Bug fixAdded unit/integration testsN/A Warning logRelated
step.ai.wrap()
editing #748