Indicate that component filter args must always be strings#71
Merged
derek-etherton-opslevel merged 2 commits intomainfrom Jul 28, 2025
Merged
Indicate that component filter args must always be strings#71derek-etherton-opslevel merged 2 commits intomainfrom
derek-etherton-opslevel merged 2 commits intomainfrom
Conversation
56f265c to
d4a80c9
Compare
rocktavious
approved these changes
Jul 28, 2025
Contributor
rocktavious
left a comment
There was a problem hiding this comment.
Look at that it even fixes the nesting!
d4a80c9 to
b505b6f
Compare
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
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.
Problem
Our components API only accepts strings for args, but agents will often try to pass numbers.
Solution
Add a note to the input that Arg must always be string.
Checklist