[ex. docs] older "Quickstart" adjustment towards quick templating, split into GraphState and MessageState #1335
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
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.
Hello LangChain!
Initially, I noticed this older quickstart had an import issue, specifically
STARTwas not imported fromlanggraph.graph. After fixing it and looking for more examples ofMessageStategraph implementation that the quickstart was using, there wasn't a clear distinction between the usage differences ofMessageStateandGraphStatefrom the get-go.These 2 boilerplate quickstarts would help kickstart someone going in either direction while also giving them the ability to see the minor differences. I also referenced them to library definitions if they would like more information and a possible next step in agentic workflow.