Jd
JSON diff and patch
Install / Use
/learn @josephburnett/JdREADME
JSON diff and patch
jd is a commandline utility and Go library for diffing and patching
JSON and YAML values. It supports a native jd format (similar to
unified format) as well as JSON Merge Patch (RFC
7386) and a subset of
JSON Patch (RFC
6902). Try it out at
http://play.jd-tool.io/.
Example
Diff jd a.json b.json:
{"foo":["bar","baz"]}
{"foo":["bar","bam","boom"]}
Output:
@ ["foo",1]
"bar"
- "baz"
+ "bam"
+ "boom"
]
Features
- Human-friendly format, similar to Unified Diff.
- Produces a minimal diff between array elements using LCS algorithm.
- Adds context before and after when modifying an array to prevent bad patches.
- Create and apply structural patches in jd, patch (RFC 6902) and merge (RFC 7386) patch formats.
- Translates between patch formats.
- Includes Web Assembly-based UI (no network calls).
Installation
GitHub Action:
- name: Diff A and B
id: diff
uses: josephburnett/jd@v2.1.2
with:
args: a.json b.json
- name: Print the diff
run: echo '${{ steps.diff.outputs.output }}'
- name: Check the exit code
run: if [ "${{ steps.diff.outputs.exit_code }}" != "1" ]; then exit 1; fi
To get the jd commandline utility:
- run
brew install jd, or - run
mise use -g jd@latestif you are using mise, or - run
go install github.com/josephburnett/jd/v2/jd@latest, or - visit https://github.com/josephburnett/jd/releases/latest and download the pre-built binary for your architecture/os, or
- run in a Docker image
jd(){ docker run --rm -i -v $PWD:$PWD -w $PWD josephburnett/jd "$@"; }.
To use the jd web UI:
- visit http://play.jd-tool.io/, or
- run
jd -port 8080and visit http://localhost:8080.
Note: to include the UI when building from source, use the Makefile.
Command line usage
Usage: jd [OPTION]... FILE1 [FILE2]
Diff and patch JSON files.
Prints the diff of FILE1 and FILE2 to STDOUT.
When FILE2 is omitted the second input is read from STDIN.
When patching (-p) FILE1 is a diff.
Options:
-color Print color diff.
-p Apply patch FILE1 to FILE2 or STDIN.
-o=FILE3 Write to FILE3 instead of STDOUT.
-opts='[]' JSON array of options. Supports global options and PathOptions.
Global: ["SET"], ["MULTISET"], [{"precision":0.1}], [{"setkeys":["id"]}], ["DIFF_ON"], ["DIFF_OFF"]
PathOptions target specific paths: [{"@":["path"],"^":["SET"]}]
Example: [{"@":["users"],"^":["SET"]},{"@":["scores",0],"^":[{"precision":0.1}]}]
-set Treat arrays as sets. Same as -opts='["SET"]'.
-mset Treat arrays as multisets (bags). Same as -opts='["MULTISET"]'.
-setkeys Keys to identify set objects. Same as -opts='[{"setkeys":["key1","key2"]}]'.
-yaml Read and write YAML instead of JSON.
-port=N Serve web UI on port N
-precision=N Maximum absolute difference for numbers to be equal.
Same as -opts='[{"precision":N}]'. Example: -precision=0.00001
-f=FORMAT Read and write diff in FORMAT "jd" (default), "patch" (RFC 6902) or
"merge" (RFC 7386)
-t=FORMATS Translate FILE1 between FORMATS. Supported formats are "jd",
"patch" (RFC 6902), "merge" (RFC 7386), "json" and "yaml".
FORMATS are provided as a pair separated by "2". E.g.
"yaml2json" or "jd2patch".
Examples:
jd a.json b.json
cat b.json | jd a.json
jd -o patch a.json b.json; jd patch a.json
jd -set a.json b.json
jd -f patch a.json b.json
jd -f merge a.json b.json
jd -opts='[{"@":["items"],"^":["SET"]}]' a.json b.json
jd -opts='[{"@":["temperature"],"^":[{"precision":0.1}]}]' a.json b.json
Command Line Option Details
setkeys This option determines what keys are used to decide if two
objects 'match'. Then the matched objects are compared, which will
return a diff if there are differences in the objects themselves,
their keys and/or values. You shouldn't expect this option to mask or
ignore non-specified keys, it is not intended as a way to 'ignore'
some differences between objects.
PathOptions: Targeted Comparison Options
PathOptions allow you to apply different comparison semantics to specific paths in your JSON/YAML data. This enables precise control over how different parts of your data are compared.
PathOption Syntax:
{"@": ["path", "to", "target"], "^": [options]}
@(At): JSON path array specifying where to apply the option^(Then): Array of options to apply at that path
Supported Options:
"SET": Treat array as a set (ignore order and duplicates)"MULTISET": Treat array as a multiset (ignore order, count duplicates){"precision": N}: Numbers within N are considered equal{"setkeys": ["key1", "key2"]}: Match objects by specified keys"DIFF_ON": Enable diffing at this path (default behavior)"DIFF_OFF": Disable diffing at this path, ignore all changes
Examples:
Treat specific array as a set while others remain as lists:
jd -opts='[{"@":["tags"],"^":["SET"]}]' a.json b.json
Apply precision to specific temperature field:
jd -opts='[{"@":["sensor","temperature"],"^":[{"precision":0.1}]}]' a.json b.json
Multiple PathOptions - SET on one path, precision on another:
jd -opts='[{"@":["items"],"^":["SET"]}, {"@":["price"],"^":[{"precision":0.01}]}]' a.json b.json
Target specific array index:
jd -opts='[{"@":["measurements", 0],"^":[{"precision":0.05}]}]' a.json b.json
Apply to root level:
jd -opts='[{"@":[],"^":["SET"]}]' a.json b.json
Ignore specific fields (deny-list approach):
jd -opts='[{"@":["timestamp"],"^":["DIFF_OFF"]}, {"@":["metadata","generated"],"^":["DIFF_OFF"]}]' a.json b.json
Allow-list approach - ignore everything except specific fields:
jd -opts='[{"@":[],"^":["DIFF_OFF"]}, {"@":["userdata"],"^":["DIFF_ON"]}]' a.json b.json
Nested override - ignore parent but include specific child:
jd -opts='[{"@":["config"],"^":["DIFF_OFF"]}, {"@":["config","user_settings"],"^":["DIFF_ON"]}]' a.json b.json
Library usage
Note: import only release commits (v2.Y.Z) because master can be unstable.
Note: the v2 library replaces the v1 (lib) library. V2 adds diff
context, minimal array diffs and hunk-level metadata. However the
format is not backward compatable. You should use v2.
import (
"fmt"
jd "github.com/josephburnett/jd/v2"
)
func ExampleJsonNode_Diff() {
a, _ := jd.ReadJsonString(`{"foo":["bar"]}`)
b, _ := jd.ReadJsonString(`{"foo":["baz"]}`)
fmt.Print(a.Diff(b).Render())
// Output:
// @ ["foo",0]
// [
// - "bar"
// + "baz"
// ]
}
func ExampleJsonNode_Patch() {
a, _ := jd.ReadJsonString(`["foo"]`)
diff, _ := jd.ReadDiffString(`
@ [1]
"foo"
+ "bar"
]
`)
b, _ := a.Patch(diff)
fmt.Print(b.Json())
// Output:
// ["foo","bar"]
}
func ExamplePathOptions() {
// Apply SET semantics to specific array path
a, _ := jd.ReadJsonString(`{"tags":["red","blue","green"], "items":[1,2,3]}`)
b, _ := jd.ReadJsonString(`{"tags":["green","red","blue"], "items":[3,2,1]}`)
// Only treat "tags" as a set, "items" remain as list
opts, _ := jd.ReadOptionsString(`[{"@":["tags"],"^":["SET"]}]`)
diff := a.Diff(b, opts...)
fmt.Print(diff.Render())
// Output:
// @ ["items",0]
// [
// + 3
// + 2
// 1
// @ ["items",3]
// 1
// - 2
// - 3
// ]
}
func ExampleMultiplePathOptions() {
a, _ := jd.ReadJsonString(`{"temp":20.12, "pressure":1013.25, "tags":["A","B","C"]}`)
b, _ := jd.ReadJsonString(`{"temp":20.15, "pressure":1013.30, "tags":["C","A","B"]}`)
// Apply precision to temp, exact match to pressure, SET semantics to tags
opts, _ := jd.ReadOptionsString(`[
{"@":["temp"],"^":[{"precision":0.1}]},
{"@":["tags"],"^":["SET"]}
]`)
diff := a.Diff(b, opts...)
fmt.Print(diff.Render())
// Output:
// @ ["pressure"]
// - 1013.25
// + 1013.3
}
func ExampleSelectiveDiffing() {
a, _ := jd.ReadJsonString(`{"userdata":"important","system":"ignore1","timestamp":"2023-01-01"}`)
b, _ := jd.ReadJsonString(`{"userdata":"changed","system":"ignore2","timestamp":"2023-01-02"}`)
// Allow-list approach: ignore everything except userdata
opts, _ := jd.ReadOptionsString(`[
{"@":[],"^":["DIFF_OFF"]},
{"@":["userdata"],"^":["DIFF_ON"]}
]`)
diff := a.Diff(b, opts...)
fmt.Print(diff.Render())
// Output:
// @ ["userdata"]
// - "important"
// + "changed"
}
func ExampleNestedOverride() {
a, _ := jd.ReadJsonString(`{"config":{"system":"val1","user_settings":"setting1"}}`)
b, _ := jd.ReadJsonString(`{"config":{"system":"val2","user_settings":"setting2"}}`)
// Ignore config changes except for user_settings
opts, _ := jd.ReadOptionsString(`[
{"@":["config"],"^":["DIFF_OFF"]},
{"@":["config","user_settings"],"^":["DIFF_ON"]}
]`)
diff := a.Diff(b, opts...)
fmt.Print(diff.Render())
// Output:
// @ ["config","user_settings"]
// - "setting1"
// + "setting2"
}
Diff Language (v2)
The jd v2 diff format is a human-readable structural diff format with context and metadata support.
Format Overview
A diff consists of:
- Options header (optional): Shows the options used to create the diff
- Metadata lines (optional): Start with
^and specify hunk-level metadata - Diff hunks: Start with
@and specify the path, followed by changes and context
Options Header
When options are provided to jd, they are displayed at the beginning of the diff to show how it was produced. Each option appears on its own line starting with ^ :
^ "SET"
^ {"precision":0.001}
@ ["items",{}]
- "old-item"
+ "new-item"
This feature helps understand:
- Whethe
