Skip to content

molsonkiko/JsonToolsNppPlugin

Repository files navigation

JsonToolsNppPlugin

Continuous Integration

Miscellaneous tools for working with JSON in Notepad++. Includes a general-purpose tree view with powerful search capabilities.

If you have any issues, see if updating to the latest release helps, and then feel free to raise an issue on GitHub. Please be sure to include diagnostic information about your system, Notepad++ version, and plugin version (go to ?->Debug Info... from the Notepad++ main menu).

Features

  1. Pretty-print JSON so that it's spread out over multiple lines.
  2. Compress JSON so that it has little or no unnecessary whitespace.
  3. Open a drop-down tree view of the document. Selecting a node in the tree navigates to the corresponding line in the document.
  4. Able to parse documents that have many different syntax errors, including but not limited to:
  5. Get the path to the current line
  6. Query and edit JSON with:
  7. A regex search form for viewing and editing CSV files, or doing find/replace operations that involve math.
  8. Parse JSON Lines documents.
  9. A form for gettting JSON from APIs or many different local files.
  10. JSON schema validation, including automatic validation based on filenames.
  11. Generation of random JSON
  12. Generation of JSON schema from JSON
  13. Automatic error checking after editing
  14. Select all JSON in a non-JSON file
  15. Quickly convert between JSON strings and raw text

Read the docs.

View past changes.

JSON file with syntax errors before and after use of JSON tools

Downloads and Installation

Go to the Releases page to see past releases.

Download latest 32-bit version

You can unzip the 32-bit download to .\Program Files (x86)\Notepad++\plugins\JsonTools\JsonTools.dll.

Download latest 64-bit version

You can unzip the 64-bit download to C:\Program Files\Notepad++\plugins\JsonTools\JsonTools.dll.

Alternatively, you can follow these installation instructions to install the latest version of the plugin from Notepad++.

System Requirements

Every version of the plugin works on Notepad++ 8.4.1 onward, although some versions of Notepad++ have problems.

Versions of the plugin from 4.10.0.3 onward are compatible with older Notepad++ (tested for 7.3.3, may be compatible with even older).

Every version up to and including 3.7.2.1 should work natively on Windows 8 or later (note: this is untested), or you must install .NET Framework 4.0. Every version beginning with 4.0.0 works on Windows 10 May 2019 update or later, or you must install .NET Framework 4.8.

Problematic Notepad++ versions

This is not a complete list of known issues with JsonTools. For that, see the issue tracker and the Changelog. This is a list of issues that emerged in recent versions of Notepad++.

Alternative tools

Notepad++

This plugin may consume huge amounts of memory when working with really huge JSON files (say 50+ megabytes). As of version 0.3.0, my HugeFiles plugin can break a JSON file up into chunks such that every chunk is syntactically valid JSON. This way you don't need to read the entire file into the text editor, and you can look at one chunk at a time. You can also use this plugin to perform simple find/replace operations on the entire file (maybe eventually allowing control over which sections of the file to edit). Finally, the plugin allows a very large JSON file to be broken up into separate syntactically valid JSON files, which may be easier to use.

JSMinNPP is a reasonable alternative, although as of v5.0.0, JsonTools has comparable performance and parsing ability.

While not a JSON plugin per se, PythonScript enables Notepad++ users to customize the editor with Python scripts. Since Python has an excellent native JSON library, you could easily use this plugin to create custom scripts for working with JSON.

Because Python has good 3rd-party packages for working with YAML and TOML (two good alternatives to JSON), PythonScript could potentially be used to allow this package to work with YAML and TOML.

VSCode

Visual Studio Code has native support for JSON with comments. Just go down to where the language is listed in the right side of the taskbar, and select JSON with Comments from the drop-down menu that appears at the top of the screen.

VSCode also has a built-in JSON tree viewer and some support for searching for keys and indices in JSON.

VSCode has many useful tools for working with JSON Schema. VSCode's JSON Schema validation is much more robust than what this plugin currently offers. You can also configure the editor to automatically use a certain JSON schema to validate JSON with a certain file path. For example, you could configure the editor to always parse files with names like *tweet*.json with the schema tweet_schema.json. Note: as of version 4.11, a similar feature exists in this plugin.

The JSON Tools plugin provides the same pretty-print and minify functionalities as this plugin.

Finally, the Encode/Decode plugin allows fast interconversion of YAML and JSON, among other things.

Emacs

Consult this list. One Emacs plugin, JSON mode, inspired the Path to current line feature of this plugin.

Python

Python's standard library JSON module is excellent, albeit limited to syntactically correct JSON according to the original JSON standard.

Python's package ecosystem is incredibly rich, so I can't possibly list all the useful tools here. Three that I've enjoyed working with are:

  1. Pandas. The Python tool for working with pretty much any kind of data. 'Nuff said.
  2. GenSON. A really user-friendly tool for JSON schema generation. Includes a CLI tool for JSON schema generation and a programmatic API. Has some tools for, e.g., merging two schemas, but I haven't used those tools as much.
  3. DeepDiff. This is super cool! It allows fast (and I mean REALLY FAST) comparison of two JSON documents to find how they differ. For instance, DeepDiff would correctly show that
{"a": [1, 2, {"b": [3, 4]}]}

and

{"a": [1, 2, {"b": [4, 4]}]}

differ in that the first element of root['a'][2]['b'] was changed from 3 to 4.

Websites

This website offers (limited) JSON->CSV conversion, pretty-printing (appears to use the same algorithm as me), minifying, JSON->XML conversion, and a pretty good tree viewer.

I expect you could find plenty of other good websites if you did some research.

Acknowledgments

Note on how JsonTools sorts strings

JsonTools sorts strings more or less the same way as other Windows applications like Microsoft Word, while Notepad++ sorts strings based on Unicode code points. This is more intuitive in some cases, and less intuitive in others.

The list below shows which things in JsonTools are case-sensitive and which are case-insensitive.

Case-sensitive sorters:

Case-insensitive sorters:

Consider this input: ["1","-2","3","o","P","ö","p"]

JsonTools case-sensitive order:

["1","-2","3","o","ö","p","P"]

JsonTools case-insensitive order:

["1","-2","3","o","ö","P","p"] (the order of the P and the p is unstable)

Notepad++ case-sensitive order:

["-2","1","3","P","o","p","ö"]

Notepad++ case-insensitive order:

["-2","1","3","o","P","p","ö"] (the order of the P and the p is unstable)

A summary of some major differences between Notepad++ and JsonTools in string sorting:

  1. The sort form ignores the leading minus sign when ordering the numbers; Notepad++ does not.
  2. The sort form orders ö between o and p (because culturally that makes sense), but Notepad++ puts ö last, because it compares the strings by Unicode code points, and non-ASCII characters like ö come after all ASCII characters.
  3. In case-sensitive sorts, JsonTools puts upper-case letters after lower-case letters, but Notepad++ does the opposite.
  4. In all sorts, JsonTools respects alphabetical order (e.g., P comes after o whether case-sensitive or not), but Notepad++ puts all upper-case letters before all lower-case letters when in case-sensitive mode.

There are many, many rules for string comparison (and I know very few of them), and I cannot possibly cover them all here. But hopefully this warning will help you not get caught off guard.