JSON Resolve pointers
JSON Resolve pointers ( object {; options} ) : Object
| Parameter | Type | Description | |
|---|---|---|---|
| object | Object | → | Object containing JSON pointers to resolve |
| ← | Object with JSON pointers resolved (only if result is an object) | ||
| options | Object | → | Options for pointer resolution |
| Function result | Object | ← | Object containing the result of the processing |
Description
The JSON Resolve pointers command resolves all the JSON pointers found in the object, with regards to options settings (if any).
JSON pointers are particularily useful to:
- embed some part of an external JSON document or reuse a part of a JSON document in other places in the same JSON document, in order to factorize information,
- express a cyclic structure in JSON,
- define a template object containing default properties stored in JSON.
Pass in the object parameter an object containing JSON pointers to be resolved (for information on JSON pointer syntax, please refer to the Defining JSON Pointers paragraph below).
Note: The source object will be updated with the result of pointer resolution after the command is executed (except if the result is not an object, see below). If you want to keep an original version of object, you may consider using the OB Copy beforehand.
Optionally, you can pass in options an object containing specific properties to be used when resolving pointers. The following properties are supported:
| Property | Value type | Description |
|---|---|---|
| rootFolder | Text | Absolute path (using standard 4D syntax) to the folder to be used to resolve relative pointers in object. Default is the database Resources folder. |
| merge | Boolean | Merge objects with pointer objects (true) instead of replacing them (false). Default is false  |
After the command is executed:
- if the result of pointer resolution is an object, object is updated and contains the resulting object.
- if the result of pointer resolution is a scalar value (i.e. a text, a number...), object is left untouched and the resulting value is returned in the "value" property of the function result.
In any cases, the command returns an object containing the following properties:
| Property | Value type | Description |
|---|---|---|
| value | Any | Result of the command processing on object. If the result is an object, it is equal to output object. |
| success | Boolean | true if all pointers have been resolved successfully |
| errors | Collection | Collection of errors if any |
| errors[].code | Number | error code |
| errors[].message | Text | error message |
| errors[].pointerURI | Text | pointer value |
| errors[].referredPath | Text | document fullpath |
Defining JSON Pointers
JSON Pointer is a standard that defines a string syntax which can be used to access a particular field or key value in the entire JSON document. The standard has been described in the RFC 6901.
A JSON pointer is, strictly speaking, a string composed of parts separated by '/'. A JSON pointer is usually found in a URI that specifies the document into which the pointer will be resolved. The fragment character "#' is used in the URI to specify the JSON pointer. By convention, a URI containing a JSON pointer can be found in a JSON object property that must be named "$ref".
{
"$ref":<path>#<json_pointer>
}
Note: 4D does not support the "-" character as reference to nonexistent arrray elements.
Recursivity and path resolution
JSON pointers are resolved recursively, which means that if a resolved pointer also contains pointers, they are resolved recursively and so on, until all pointers are resolved. In this context, all file paths found in JSON pointer URIs can be relative or absolute. They must use '/' as path delimiter and are resolved the following way:
- A relative path must not start with '/'. It is resolved relatively to the JSON document where the path string has been found,
- An absolute path starts with '/'. Only filesystem pathnames are accepted as absolute paths. For example, "/RESOURCES/templates/myfile.json" points to the file "myfile.json" located in the current database resources folder.
Notes:
- The name resolution is case sensitive.
- 4D does not resolve a path to a json file located over the network (starting with "http/https").
Example 1
This basic example illustrates how a JSON pointer can be set and replaced in an object:
// create an object with some value
var $o : Object
$o:=New object("value";42)
// create the JSON pointer object
var $ref : Object
$ref:=New object("$ref";"#/value")
// add the JSON pointer object as property
$o.myJSONPointer:=$ref
// resolve the whole and check that the pointer has been resolved
var $result : Object
$options:=New object("rootFolder";Get 4D folder(Current resources folder);"merge";True)
$result:=JSON Resolve pointers($o;$options)
If($result.success)
ALERT(JSON Stringify($result.value))
//{"value":42,"myJSONPointer":42}
Else
ALERT(JSON Stringify($result.errors))
End if
Example 2
You want to reuse the "billingAddress" as the "shippingAddress" in the following JSON object (named $oMyConfig):
{
"lastname": "Doe",
"firstname": "John",
"billingAddress": {
"street": "95 S. Market Street",
"city": "San Jose",
"state": "California"
},
"shippingAddress": { "$ref": "#/billingAddress" }
}
After executing this code:
$oResult:=JSON Resolve pointers($oMyConfig)
... the following object is returned:
{
"success": true,
"value": {
"lastname": "Doe",
"firstname": "John",
"billingAddress": {
"street": "95 S. Market Street",
"city": "San Jose",
"state": "California"
},
"shippingAddress": {
"street": "95 S. Market Street",
"city": "San Jose",
"state": "California"
}
}
}
Example 3
This example illustrates the effect of the "merge" option. You want to edit an user's rights based upon a default file.
{
"rights": {
"$ref": "defaultSettings.json#/defaultRights",
"delete": true,
"id": 456
}
}
The defaultSettings.json file contains:
{
"defaultRights":
{
"edit": true,
"add": false,
"delete": false
}
}
If you execute:
var $options : Object
$options:=New object("merge";False) //replace contents
$oResult:=JSON Resolve pointers($oMyConfig;$options)
... the resulting value is exactly the defaultSettings.json file contents:
{
"success": true,
"value": {
"rights": {
"edit": true,
"add": false,
"delete": false
}
}
}
If you execute:
var $options : Object
$options:=New object("merge";True) //merge both contents
$oResult:=JSON Resolve pointers($oMyConfig;$options)
... the resulting value is a modified version of the original object:
{
"success": true,
"value": {
"rights": {
"edit": true,
"add": false,
"delete": true,
"id": 456
}
}
}