RFC: JSON Pointer (RFC 6901) and JSON Patch (RFC 6902) support

Offen
#16,327 2 Kommentare 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

@gururaj1512 arbeitet bereits daran.

Seit 27.10.2026.

  • #16380 von @gururaj1512 — offen
  • #16388 von @gururaj1512 — offen
  • #16389 von @gururaj1512 — offen

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

RFC
Description

This issue tracks the work required to implement first-class JSON Pointer (RFC 6901) and JSON Patch (RFC 6902) utility suites across the @stdlib/utils namespace.

The goal is to provide a zero-dependency, standard-compliant, immutable patching architecture suitable for incremental document updates (such as delta updates to Vega visualization specifications):

  1. JSON Pointer (@stdlib/utils/json-pointer/*): Serves as the foundational addressing layer for identifying and resolving values within JSON documents, parsing pointer strings into reference tokens, formatting tokens, validating array indices, and enforcing prototype pollution security boundaries.
  2. JSON Patch (@stdlib/utils/json-patch/*): Implements atomic patch execution for the six standard RFC 6902 operations (add, remove, replace, move, copy, and test) using structural sharing (path-cloning) to guarantee that unmodified subtrees maintain reference equality and the original document is never mutated.

Below is the complete hierarchical and alphabetical list of packages across both namespaces, annotated with their status and task type.


Package Checklist

JSON Pointer Suite (RFC 6901)
  • @stdlib/utils/json-pointer (Top-Level Namespace Aggregator)
    • @stdlib/utils/json-pointer/format
    • @stdlib/utils/json-pointer/get
    • @stdlib/utils/json-pointer/has
    • @stdlib/utils/json-pointer/parse
    • @stdlib/utils/json-pointer/resolve
    • @stdlib/utils/json-pointer/base (Base Operations Sub-Namespace)
      • @stdlib/utils/json-pointer/base/resolve-token
      • @stdlib/utils/json-pointer/base/assert (Base Assertions Sub-Namespace)
        • @stdlib/utils/json-pointer/base/assert/is-safe-token

JSON Patch Suite (RFC 6902)
  • @stdlib/utils/json-patch (Top-Level Namespace Aggregator)
    • @stdlib/utils/json-patch/apply
    • @stdlib/utils/json-patch/validate
    • @stdlib/utils/json-patch/ops (Patch Operations Sub-Namespace)
      • @stdlib/utils/json-patch/ops/add
      • @stdlib/utils/json-patch/ops/copy
      • @stdlib/utils/json-patch/ops/move
      • @stdlib/utils/json-patch/ops/remove
      • @stdlib/utils/json-patch/ops/replace
      • @stdlib/utils/json-patch/ops/assert
    • @stdlib/utils/json-patch/base (Base Operations Sub-Namespace)
      • @stdlib/utils/json-patch/base/delete-in
      • @stdlib/utils/json-patch/base/insert-in
      • @stdlib/utils/json-patch/base/set-in
      • @stdlib/utils/json-patch/base/shallow-clone
Related Issues

Related issues # , # , and # .

Questions

No.

Other

No.

Checklist
  • I have read and understood the Code of Conduct.
  • Searched for existing issues and pull requests.
  • The issue name begins with RFC:.
Vorherrschende Sprache
JavaScript
Sterne
6k
Forks
1.3k
Ø Merge
1 T. 21 Std.
Gemergte PRs (30 T.)
224

Entwicklungsumgebung

In Codespaces öffnen

Startet den Dev-Container des Projekts im Browser, mit Ihrem eigenen GitHub-Konto.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus stdlib-js/stdlib

Alle Issues in stdlib-js/stdlib

Ähnliche Issues

Weitere Issues zu JavaScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.