v1.5 [Jul 16, 2013]
OAuth 2.0 Support
• OAuth 2.0 is now supported for the following providers: bitly, Facebook, Foursquare, GitHub, Google, Instagram
• You can setup new OAuth 2.0 authorizations from "HTTP Client" window, by selecting "+"->"New OAuth 2.0 Authorization", or from HTTP request's details by selecting "OAuth"->"Add..."
• Once you have added and setup an OAuth 2.0 authorization you can attach it to a HTTP request from "OAuth" pull down control. Once this is done, JSON Editor will take care of refreshing and attaching access token to your request.
Other changes and improvements
• If the HTTP response doesn't contain a "Content-Type" HTTP header then the response will be treated as text.
• If the HTTP response has a "Content-Type" of "text/javascript" then the response will be treated as JSON, thus no warnings will be shown when you try to "Beautify" or "Open in New JSON Document"
• Fixed a crash which might occur when getting HTTP response from server.
v1.3 [Jul 7, 2019]
Improvements
• The keys for the items enclosed in an array are now displayed using a lighter gray color, to underline that they are not editable.
• When an item which is contained in an Object (Dictionary) is embedded in an Array or Object, then the item which is created as a result will retain the key of the item which was embedded. Note that this works only when embedding a single item, for multiple items the name of the key will continue to start with "New item -".
Bug fixing
• The expanded items no longer (annoyingly) collase when you move or embed them in an array or dictionary.
Introduced in Version 1.31
Improvements
• Adds support for regular expression in the Replace field. This works as long as you perform a search for regular expression. The technique used to do the regular expression replace is "template matching", where you can use $0, $1, $2 and so on, to specify which text of the capture group will be substitued. $0 will be replaced by the contents of the matched range, $1 by the contents of the first capture group, and so on. Additionally, backslash character '\' can be used to suppres any special meaning for the next character. Backslash escaping in replace text is only required for '$' and '\', but may be used on any other character without bad effects. For additional information, see NSRegularExpression.
• The "Editor" menu was split into two menus: "Tree Editor", which contains the items which make sense while you're in JSON Tree Editor, and "Text Editor" which contains the items which make sense in JSON Text Editor mode.
• Adds preference for how much to indent the text. This is available from "Preferences" -> "View and Edit" -> "Indent using".
• Completely removed the sending of crash reports and analytics from the app. Note that until now the sending happened only if you explicitly allowed it to happen.
Introduced in Version 1.30
Improvements
• Adds "PATCH" in the list of HTTP verbs support by the HTTP Client.
Introduced in Version 1.29
Improvements
• Adds support to turn off the "+" and "-" buttons which appear on the row tracked by mouse. This can be done from Preferences (Command + ,) , by unchecking "Show "+" and "-" buttons on the row tracked by mouse" option from "View and Edit" tab.
• User's consent is now obtained before collecting crash reports and analytics.
Bug fixing
• Fixes the printing in Dark mode.
Introduced in Version 1.28
Bug fixing
• Fixes an issue where sometimes the response of a web service failed to be opened from command-line.
Introduced in Version 1.27
Bug fixing
• Fixes an issue where sometimes the response of a web service failed to be opened from command-line.
