-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Add support for specifying null values for tool fields
#850
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
Add support for specifying null values for tool fields
#850
Conversation
null values for tool fields
|
Hi @gregsaab! Interestingly, there is another PR @olaservo is working on where the challenge is to send |
Hey @cliffhall yeah, I saw that soon after I submitted this. Thought it would be worth having an alternative approach in the mix! |
|
@gregsaab can you merge main on your branch and resolve conflicts? There have been some changes to the |
@cliffhall done 3adddfb |
cliffhall
left a comment
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.



This adds the ability to specify a
nullvalue for nullable fields by conditionally rendering anullcheckbox when a field has anulltype in the array. If the checkbox is selected, the input will be disabled.I chose checkboxes over supporting a value of
"null"to make behavior explicit, obvious, and not to affect cases where you actually want to send "null" as a value.Example:
Note
When reviewing, hide whitespace changes

Motivation and Context
At present, there is no way to specify a
nullvalue for a field.How Has This Been Tested?
Breaking Changes
No
Types of changes
Checklist