langchain-ai/langgraphjs
1
0
Fork 0
mirror of https://github.com/langchain-ai/langgraphjs.git synced 2026-07-23 17:45:23 -04:00
Code Issues 108 Packages Projects Releases 20 Wiki Activity

Why thread_id and checkpoint_id are not camel cased? #39

New Issue
Closed
opened 2026-02-15 17:05:59 -05:00 by yindo · 2 comments
yindo commented 2026-02-15 17:05:59 -05:00
Owner
Copy Link
Copy Source

Originally created by @vianvio on GitHub (Jun 19, 2024).

First time I saw thread_id in document example, I thought it was translated from the python example, can can be customized. So when I try my own demo, I just changed it to threadId. When it goes, the memory got an undefined in the storage key, which makes me confused.

Finnaly I found the variable definition in the source code, but it is different from all other variables. Why do we specially use thread_id and checkpoint_id here?

Originally created by @vianvio on GitHub (Jun 19, 2024). First time I saw thread_id in document example, I thought it was translated from the python example, can can be customized. So when I try my own demo, I just changed it to threadId. When it goes, the memory got an undefined in the storage key, which makes me confused. Finnaly I found the variable definition in the source code, but it is different from all other variables. Why do we specially use thread_id and checkpoint_id here?
yindo closed this issue 2026-02-15 17:05:59 -05:00
yindo commented 2026-02-15 17:06:00 -05:00
Author
Owner
Copy Link
Copy Source

@hwchase17 commented on GitHub (Jun 19, 2024):

is this referencing the checkpointer? or the python/js sdks for intereacting with the server?

@hwchase17 commented on GitHub (Jun 19, 2024): is this referencing the checkpointer? or the python/js sdks for intereacting with the server?
yindo commented 2026-02-15 17:06:00 -05:00
Author
Owner
Copy Link
Copy Source

@dqbd commented on GitHub (Jun 17, 2025):

Hello! I think this is by design with the goal being having consistent access to thread ID / checkpoint ID when consuming a run stream, regardless of JS / Python

@dqbd commented on GitHub (Jun 17, 2025): Hello! I think this is by design with the goal being having consistent access to thread ID / checkpoint ID when consuming a run stream, regardless of JS / Python
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
checkpointer
docs-needed
documentation
enhancement
good first issue
good writeup
help wanted
invalid
langgraph-supervisor
open-swe-auto
platform
prebuilt
pull-request
Mirrored from GitHub Pull Request
 question
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langchain-ai/langgraphjs#39
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?