Bugfixes

- Bugfix: Updated the members function to fit EE6.x
- Added json_pretty_print parameter for better readable output. Handy in the development stage
- Code cleanup
- Updated README

Author: Zignature

README.markdown

@@ -19,7 +19,7 @@ Since legacy custom fields do not have their own table they will work fine eithe
 
 ***Fluid fieldtype***
 
-Fluid fieldtype is not supported.
+Fluid fieldtype is not yet supported.
 
 ## Installation
 
@@ -29,23 +29,27 @@ Fluid fieldtype is not supported.
 
 ### `xhr="yes"`
 
-Set xhr to yes to only output data when an XMLHttpRequest is detected. Do not set this to yes if you are using JSONP, as JSONP requests are not true XHMLHttpRequests.
+Set `xhr` to yes to only output data when an XMLHttpRequest is detected. Do not set this to yes if you are using JSONP, as JSONP requests are not true XHMLHttpRequests.
 
 ### `terminate="yes"`
 
-Set terminate to yes to terminate the template and output your json immediately, with Content-Type headers.
+Set `terminate=` to yes to terminate the template and output your json immediately, with Content-Type headers.
+
+### `json_pretty_print="yes"`
+
+For a better readable output. Combine with `terminate="yes"`. It's handy in the development stage.
 
 ### `fields="title|url_title"`
 
 Specify which fields you wish to have in the array. Separate multiple fields by a pipe character. If you do not specify fields, you will get all of the default fields' data. The primary key (`entry_id` for entries, `member_id` for members) will always be present and cannot be suppressed by this parameter.
 
 ### `content_type="text/javascript"`
 
-Set a custom Content-Type header. The default is "application/json", or "application/javascript" if using JSONP. Headers are only sent when terminate is set to "yes".
+Set a custom Content-Type header. The default is "application/json", or "application/javascript" if using JSONP. Headers are only sent when `terminate` is set to "yes".
 
 ### `jsonp="yes"`
 
-Set jsonp to yes to enable a JSONP response. You must also specify a valid callback. You are encouraged to set terminate to yes when using JSONP.
+Set `jsonp` to yes to enable a JSONP response. You must also specify a valid callback. You are encouraged to set `terminate` to yes when using JSONP.
 
 ### `callback="yourCallbackFunction"`
 
@@ -139,15 +143,15 @@ for (i in data) {
 }
 ```
 
-If you require a different output format for the date fields, set the date_format= parameter. This uses the php date() function. common formats include "U" (unix timestamp in seconds), "c" (ISO 8601) or "Y-m-d H:i" (2011-12-24 19:06).
+If you require a different output format for the date fields, set the `date_format=` parameter. This uses the php date() function. common formats include "U" (unix timestamp in seconds), "c" (ISO 8601) or "Y-m-d H:i" (2011-12-24 19:06).
 
 ## json:entries
 
 ```
 {exp:json:entries channel="news"}
 ```
 
-json:entries is a single tag, not a tag pair. Use channel:entries parameters to filter your entries.
+`json:entries` is a single tag, not a tag pair. Use channel:entries parameters to filter your entries.
 
 #### json:entries Default Fields
 
@@ -174,18 +178,26 @@ This will add categories to the entries response
 
 ##### `show_category_group="1|2"`
 
-When paired with show_categories="yes", this will display only categories from the specified groups.
+When paired with `show_categories="yes"`, this will display only categories from the specified groups.
 
 #### json:entries Custom Fields
 
 Most custom fields will just return the raw column data from the `exp_channel_data` database table. The following fieldtypes will provide custom data. You *must* specify the `channel` parameter to get custom fields.
 
-##### Matrix
+##### Date
 
-The data will include an array of Matrix rows, including the row_id and the column names:
+The data will be the Unix timestamp, accurate to milliseconds. This is because the native JavaScript Date object accepts a millisecond-based timestamp in its constructor.
 
 ```
-your_matrix_field: [
+your_date_field: 1385661660000
+```
+
+##### Grid
+
+The data will include an array of Grid rows, including the row_id and the column names:
+
+```
+your_grid_field: [
   {
     row_id: 1,
     my_col_name: "foo",
@@ -199,19 +211,21 @@ your_matrix_field: [
 ]
 ```
 
-##### Grid
+##### File Grid (EE v5.1+)
 
-The data will include an array of Grid rows, including the row_id and the column names:
+The data will include an array of File Grid rows including the row_id, the file and the optional extra column names:
 
 ```
-your_grid_field: [
+your_file_grid_field: [
   {
     row_id: 1,
+    file: "URL-to-your-file",
     my_col_name: "foo",
     other_col_name: "bar"
   },
   {
     row_id: 2,
+    file: "URL-to-your-file",
     my_col_name: "baz",
     other_col_name: "qux"
   }
@@ -226,15 +240,7 @@ The data will include an array of related entry IDs:
 your_relationships_field: [1, 2]
 ```
 
-##### Playa
-
-The data will include an array of related entry IDs:
-
-```
-your_playa_field: [1, 2]
-```
-
-##### Assets
+##### Assets (not tested with JSON v2+)
 
 ```
 your_assets_field: [
@@ -289,7 +295,7 @@ your_assets_field: [
 
 *NOTE: image manipulation urls are only available to Assets files store locally, not on Amazon S3 or Google Storage.*
 
-##### Channel Files
+##### Channel Files (not tested with JSON v2+)
 
 ```
 your_channel_files_field: [
@@ -334,12 +340,31 @@ your_channel_files_field: [
 ]
 ```
 
-##### Date
+##### Matrix (not tested with JSON v2+)
 
-The data will be the Unix timestamp, accurate to milliseconds. This is because the native JavaScript Date object accepts a millisecond-based timestamp in its constructor.
+The data will include an array of Matrix rows, including the row_id and the column names:
 
 ```
-your_date_field: 1385661660000
+your_matrix_field: [
+  {
+    row_id: 1,
+    my_col_name: "foo",
+    other_col_name: "bar"
+  },
+  {
+    row_id: 2,
+    my_col_name: "baz",
+    other_col_name: "qux"
+  }
+]
+```
+
+##### Playa (not tested with JSON v2+)
+
+The data will include an array of related entry IDs:
+
+```
+your_playa_field: [1, 2]
 ```
 
 ## json:search
@@ -456,12 +481,17 @@ function yourCallbackFunction(data) {
 
 ## Changelog
 
+### v.2.5.2
+
+- Bugfix: Updated the `members` function to handle both legacy (pre EE4) and newer member data
+- Added `json_pretty_print` parameter for better readable output. Handy in the development stage
+- Code cleanup
+- Updated README
+
 ### v2.5.1
 
 - Bugfix: Removed all remnants of fluid field data, since the Fluid fieldtype is not (yet) supported. The remnant data is unusable at this point. Working on support for Fluid fieldtype
-- Bugfix: Updated the `members` function to fit EE6.x
 - Changed `addon.setup.php` and cleaned it up
-- **Note:** not tested with Assets, Matrix, Playa and Channel Files fieldtypes/modules
 
 ### v2.5.0
 
@@ -470,15 +500,13 @@ function yourCallbackFunction(data) {
 - Added support for File Grid fieldtype
 - Added support for legacy custom fields and data (EE2 and EE3 custom fields and data) for compatibility with upgraded versions of EE4+
 - Added `/system/user/addons/json/icon.png` for the EE6 control panel
-- **Note:** not tested with Assets, Matrix, Playa and Channel Files fieldtypes/modules
 
 ### v1.1.9
 
-- EE3 compatibility
+- ExpressionEngine 3.x compatibility
 - Added relationships support for grids as per [ahebrank's](https://github.com/ahebrank) [commit](https://github.com/rsanchez/json/pull/65)
 - Added `/system/user/addons/json/addon.setup.php` for EE3
 - Added `/system/user/addons/json/README.md` for the add-on manual in the control panel (as of EE3)
-- **Note:** not tested with Assets, Matrix and Playa
 
 ## Attribution