Fix Return Type for create_team_supervisor Function to Reflect Correc… #2525
Conversation
This file contains 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
…t Output Structure I noticed that the return type of the create_team_supervisor function was incorrectly defined as -> str, but the function does not simply return a string. Instead, it returns a complex object involving a series of chained operations, including function bindings and JSON parsing. To reflect this behavior accurately, I updated the return type to -> Any, which is more appropriate for the dynamic nature of the return value.
|
Thank you for your contribution -- this code is actually outdated and is no longer used. See the latest version here https://langchain-ai.github.io/langgraph/tutorials/multi_agent/hierarchical_agent_teams/#create-tools |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
…t Output Structure
I noticed that the return type of the create_team_supervisor function was incorrectly defined as -> str, but the function does not simply return a string. Instead, it returns a complex object involving a series of chained operations, including function bindings and JSON parsing. To reflect this behavior accurately, I updated the return type to -> Any, which is more appropriate for the dynamic nature of the return value.