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

Langgraph allows you to invoke a graph using state properties that do not exist, and then displays these in langsmith in the __start__ node #207

New Issue
Closed
opened 2026-02-15 17:17:19 -05:00 by yindo · 1 comment
yindo commented 2026-02-15 17:17:19 -05:00
Owner
Copy Link
Copy Source

Originally created by @ashburnham on GitHub (Mar 20, 2025).

If I invoke a graph which has one state property foo

graph.invoke({
  foo: 1,
  bar: 2,
})

The in Langsmith I will see both properties in the __start__ node, and the the invalid property the disappears when it gets to the following node in the graph.

This is confusing as bar should not be able to exist in the graph state.

Proposed behaviour:

  • graph.invoke to be type-safe so that it cannot be invoked with invalid properties.
  • invalid properties not to show at all in the state in Langsmith
Originally created by @ashburnham on GitHub (Mar 20, 2025). If I invoke a graph which has one state property foo ``` graph.invoke({ foo: 1, bar: 2, }) ``` The in Langsmith I will see both properties in the `__start__` node, and the the invalid property the disappears when it gets to the following node in the graph. This is confusing as bar should not be able to exist in the graph state. Proposed behaviour: - `graph.invoke` to be type-safe so that it cannot be invoked with invalid properties. - invalid properties not to show at all in the state in Langsmith
yindo closed this issue 2026-02-15 17:17:19 -05:00
yindo commented 2026-02-15 17:17:20 -05:00
Author
Owner
Copy Link
Copy Source

@dqbd commented on GitHub (May 28, 2025):

Hello!

graph.invoke to be type-safe so that it cannot be invoked with invalid properties.

I believe that you're most likely running Typescript with strict: false in tsconfig.json. With strict: true, the TypeScript will warn you that an invalid property is being sent.

invalid properties not to show at all in the state in Langsmith
Will close this as won't fix, as I believe that this is the expected behaviour.

@dqbd commented on GitHub (May 28, 2025): Hello! > graph.invoke to be type-safe so that it cannot be invoked with invalid properties. I believe that you're most likely running Typescript with `strict: false` in `tsconfig.json`. With `strict: true`, the TypeScript will warn you that an invalid property is being sent. > invalid properties not to show at all in the state in Langsmith Will close this as won't fix, as I believe that this is the expected behaviour.
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#207
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?