Skip to content
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

[hub] [backend] iron out pydantic versioning for templete, invocation params, content parts #6168

Open
Tracked by #5582
mikeldking opened this issue Jan 24, 2025 · 0 comments
Assignees

Comments

@mikeldking
Copy link
Contributor

mikeldking commented Jan 24, 2025

Currently we don't have sufficient confidence that our current pydantic types sufficiently cover certain blocks of unstructured JSON - notably

  • invocation params
  • the ability to put other keys like citations inside of a content text part (test)

We also need to have some sort of documentation on how the pydantic versioning will work in the future if we ever need to introduce a breaking change to the schema of say a tool or a content part.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 📘 Todo
Development

No branches or pull requests

3 participants