-
Notifications
You must be signed in to change notification settings - Fork 297
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Hide tool button on non-supported providers, Display errors for missing invocation params #5470
fix: Hide tool button on non-supported providers, Display errors for missing invocation params #5470
Conversation
47b4b28
to
a4ff918
Compare
66ac3c9
to
9ea9c1f
Compare
Need to also hide defined tools for gemini |
currentInvocationParametersMap.get(paramKeyName)?.[ | ||
toCamelCase( | ||
param.invocationInputField || "" | ||
) as keyof InvocationParameterInput | ||
] != null || |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we should pull this out to make it a bit easier to read. The toCamelCase is because all params are stored like that in the map? when would these things be out of sync? one needing to be camelCased cause the other already had been
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good callout, done
…ache results in store Additionally moves invocation param filtering to just before making the completion queries, not when the invocation param form is opened
…ram fields are not provided
9ea9c1f
to
0c2d35d
Compare
filter-invalid-params-show-warnings.mov
Note the new warnings when params are not filled in.
Also note that I am able to submit gemini with a tool definition configured; It now gets stripped out and it was not before. This is possible because the completion submission logic is now aware of which parameters are supported by the api.
Resolves #5462
Resolves #5431