Improve usage of JSON schemas in LangGraph adapter #88
Conversation
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
…hema instead of pydantic objects
oracle-contributor-agreement
bot
added
the
OCA Verified
|
Internal regression failed: Build ID #271 |
|
Internal regression failed: Build ID #272 |
sonleoracle
approved these changes
Jan 30, 2026
pyagentspec/src/pyagentspec/adapters/langgraph/_langgraphconverter.py
Outdated
Show resolved
Hide resolved
dhilloulinoracle
approved these changes
Jan 30, 2026
|
Internal regression failed: Build ID #274 |
|
Internal regression failed: Build ID #276 |
|
Internal regression failed: Build ID #277 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
LangGraph often supports both pydantic models and json schema definitions when defining types (e.g., inputs and outputs of tools, agents, etc.). The main difference is that when providing pydantic models, the output is going to be of that type, making the compliance with agent spec typing system complicated. We move to JSON schema typing definition where possible.