langchain-ai/docs
1
0
Fork 0
mirror of https://github.com/langchain-ai/docs.git synced 2026-08-24 22:01:29 -04:00
Code Issues 490 Packages Projects Releases Wiki Activity

[PR #742] [MERGED] Improve clarity in JSON loader documentation #975

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

📋 Pull Request Information

Original PR: https://github.com/langchain-ai/docs/pull/742
Author: @anu-rock
Created: 10/4/2025
Status: ✅ Merged
Merged: 10/6/2025
Merged by: @lnhsingh

Base: prod ← Head: patch-1

📝 Commits (1)

  • 5a458a4 Improve clarity in JSON loader documentation

📊 Changes

1 file changed (+27 additions, -28 deletions)

View changed files

📝 build/oss/javascript/integrations/document_loaders/file_loaders/json.mdx (+27 -28)

📄 Description

Overview

  • Expand the no JSON pointer example for clarity.
  • Correct the output of JSON pointer example.
  • Minor copy changes for correctness.

Type of change

Type: Fix typo/bug/link/formatting

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
  • (Internal team members only / optional) I have created a preview deployment using the Create Preview Branch workflow

🔄 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/742 **Author:** [@anu-rock](https://github.com/anu-rock) **Created:** 10/4/2025 **Status:** ✅ Merged **Merged:** 10/6/2025 **Merged by:** [@lnhsingh](https://github.com/lnhsingh) **Base:** `prod` ← **Head:** `patch-1` --- ### 📝 Commits (1) - [`5a458a4`](https://github.com/langchain-ai/docs/commit/5a458a454b206e1ccb93726a07d31d573951b6ba) Improve clarity in JSON loader documentation ### 📊 Changes **1 file changed** (+27 additions, -28 deletions) <details> <summary>View changed files</summary> 📝 `build/oss/javascript/integrations/document_loaders/file_loaders/json.mdx` (+27 -28) </details> ### 📄 Description ## Overview <!-- Brief description of what documentation is being added/updated --> - Expand the no JSON pointer example for clarity. - Correct the output of JSON pointer example. - Minor copy changes for correctness. ## Type of change **Type:** Fix typo/bug/link/formatting ## Checklist <!-- Put an 'x' in all boxes that apply --> - [x] I have read the [contributing guidelines](README.md) - [x] I have tested my changes locally using `docs dev` - [x] 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 - (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) --- <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:21:29 -05:00
yindo closed this issue 2026-02-17 17:21:29 -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#975
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?