You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.e.md
+17-4Lines changed: 17 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ The `jsonfiddle` makes it easy to look at the JSON data from different aspects.
34
34
35
35
$ jsonfiddle fmt -i test/Customer.json
36
36
37
-
#### > {{cat "test/CustomerI.ref" | color "json"}}
37
+
#### > {{cat "test/CustomerSI.ref" | color "json"}}
38
38
39
39
### Compact
40
40
@@ -78,15 +78,28 @@ Thus all the JSON comparison tools I found are failing under such hash request.
78
78
- Sorting the JSON data fields recursively and producing plain text file (via `jsonfiddle sort`), then use the state-of-the-art text comparison tools to compare them is the best approach, for my above scenario.
79
79
- For extremely long and very complicated JSONs, converting json to abstract Go struct (via `jsonfiddle j2s`) is the quickest approach to compare them at higher level.
80
80
81
+
# Download binaries
82
+
83
+
- The latest binary executables are available under
84
+
https://github.com/go-jsonfile/{{.Name}}/releases
85
+
as the result of the Continuous-Integration process.
86
+
- I.e., they are built right from the source code during every git tagging commit automatically by [travis-ci](https://travis-ci.org/).
87
+
- Pick & choose the binary executable that suits your OS and its architecture. E.g., for Linux, it would most probably be the `{{.Name}}_linux_VER_amd64` file. If your OS and its architecture is not available in the download list, please let me know and I'll add it.
88
+
- You may want to rename it to a shorter name instead, e.g., `{{.Name}}`, after downloading it.
@@ -236,15 +258,28 @@ Thus all the JSON comparison tools I found are failing under such hash request.
236
258
- Sorting the JSON data fields recursively and producing plain text file (via `jsonfiddle sort`), then use the state-of-the-art text comparison tools to compare them is the best approach, for my above scenario.
237
259
- For extremely long and very complicated JSONs, converting json to abstract Go struct (via `jsonfiddle j2s`) is the quickest approach to compare them at higher level.
238
260
261
+
# Download binaries
262
+
263
+
- The latest binary executables are available under
as the result of the Continuous-Integration process.
266
+
- I.e., they are built right from the source code during every git tagging commit automatically by [travis-ci](https://travis-ci.org/).
267
+
- Pick & choose the binary executable that suits your OS and its architecture. E.g., for Linux, it would most probably be the `jsonfiddle_linux_VER_amd64` file. If your OS and its architecture is not available in the download list, please let me know and I'll add it.
268
+
- You may want to rename it to a shorter name instead, e.g., `jsonfiddle`, after downloading it.
0 commit comments