langchain-ai/docs
1
0
Fork 0
mirror of https://github.com/langchain-ai/docs.git synced 2026-07-22 12:25:55 -04:00
Code Issues 490 Packages Projects Releases Wiki Activity

[PR #1073] [MERGED] docs[graph-api]: should you use END instead “__end__” #1274

New Issue
Closed
opened 2026-02-17 17:22:03 -05:00 by yindo · 0 comments
yindo commented 2026-02-17 17:22:03 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/langchain-ai/docs/pull/1073
Author: @Athroniaeth
Created: 10/21/2025
Status: ✅ Merged
Merged: 10/22/2025
Merged by: @lnhsingh

Base: main ← Head: patch-6

📝 Commits (2)

  • d7050f4 docs[graph-api]: should you use END instead “end”
  • d4ab38c Merge branch 'main' into patch-6

📊 Changes

1 file changed (+3 additions, -3 deletions)

View changed files

📝 src/oss/langgraph/use-graph-api.mdx (+3 -3)

📄 Description

When I use Literal[END] i have this message from PyCharm IDE : 'Literal' may be parameterized with literal ints, byte and unicode strings, bools, Enum values, None, other literal types, or type aliases to other literal type

I think it's better to use what the library offers in case it changes.

Further down the page, there is end used. What is the recommended method? Is the IDE message deprecated? (I let a maintainer review and decide and update if need.)

Overview

Type of change

Type: [Replace with: New documentation page / Update existing documentation / Fix typo/bug/link/formatting / Remove outdated content / Other]

Related issues/PRs

  • GitHub issue:
  • Feature PR:
  • Linear issue:
  • Slack thread:

Checklist

  • I have read the contributing guidelines
  • I have tested my changes locally using docs dev
  • All code examples have been tested and work correctly
  • I have used root relative paths for internal links
  • I have updated navigation in src/docs.json if needed
  • I have gotten approval from the relevant reviewers

Additional notes

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/langchain-ai/docs/pull/1073 **Author:** [@Athroniaeth](https://github.com/Athroniaeth) **Created:** 10/21/2025 **Status:** ✅ Merged **Merged:** 10/22/2025 **Merged by:** [@lnhsingh](https://github.com/lnhsingh) **Base:** `main` ← **Head:** `patch-6` --- ### 📝 Commits (2) - [`d7050f4`](https://github.com/langchain-ai/docs/commit/d7050f4e8d34efd9dea1aee3f5d22ef12240b4c5) docs[graph-api]: should you use END instead “__end__” - [`d4ab38c`](https://github.com/langchain-ai/docs/commit/d4ab38c0e53283c36c712b1c0d008b2b6e491248) Merge branch 'main' into patch-6 ### 📊 Changes **1 file changed** (+3 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `src/oss/langgraph/use-graph-api.mdx` (+3 -3) </details> ### 📄 Description When I use Literal[END] i have this message from PyCharm IDE : `'Literal' may be parameterized with literal ints, byte and unicode strings, bools, Enum values, None, other literal types, or type aliases to other literal type` I think it's better to use what the library offers in case it changes. Further down the page, there is __end__ used. What is the recommended method? Is the IDE message deprecated? (I let a maintainer review and decide and update if need.) ## Overview <!-- Brief description of what documentation is being added/updated --> ## Type of change **Type:** [Replace with: New documentation page / Update existing documentation / Fix typo/bug/link/formatting / Remove outdated content / Other] ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes #123" or "fixes #123" or "resolves #123" For regular references without auto-closing, just use: - "#123" or "See issue #123" Examples: - closes #456 (will auto-close issue #456 when PR is merged) - See #789 for context (will reference but not auto-close issue #789) --> - GitHub issue: - Feature PR: <!-- For LangChain employees, if applicable: --> - Linear issue: - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [ ] I have read the [contributing guidelines](README.md) - [ ] I have tested my changes locally using `docs dev` - [ ] All code examples have been tested and work correctly - [ ] I have used **root relative** paths for internal links - [ ] I have updated navigation in `src/docs.json` if needed - I have gotten approval from the relevant reviewers ## Additional notes <!-- Any other information that would be helpful for reviewers --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-17 17:22:03 -05:00
yindo closed this issue 2026-02-17 17:22:03 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
deepagents
docs-infra
external
external
help wanted
integration
internal
internal
javascript
js/ts
langchain
langgraph
langsmith
needs-title
pull-request
Mirrored from GitHub Pull Request
 python
reference
No Label pull-request
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/docs#1274
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?