-
Notifications
You must be signed in to change notification settings - Fork 11
feat: add type validation to params when tool is invoked #129
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
Conversation
* ci: add release please config * chore: add initial version * chore: specify initial version as string * chore: Update .release-please-manifest.json * chore: add empty json * chore: small change * chore: try fixing config * chore: try fixing config again * chore: remove release-as * chore: add changelog sections * chore: better release notes * chore: better release notes * chore: change toolbox-langchain version * chore: separate PRs for packages * chore: change PR style
By default, Pydantic models treat all fields without defaults as keyword-only arguments in their generated init signature. This means, if we use the pydantic model signature ( I tried using |
Co-authored-by: Anubhav Dhawan <anubhav756@gmail.com>
Adds type validation to inputs when a tool is invoked using pydantic.