Here's the output when you select the Support Type Extensions checkbox: When you deselect this checkbox, the SnapLogic-specific syntax is not used the Snap uses a string representation for each of the special objects.
The Support Type Extensions state affects the JSON Formatter's output. Here's the same Mapper when you select the Support Type Extensions checkbox.
Similarly, here's a Mapper Snap showing the JSON Parser output when you deselect the Support Type Extensions checkbox. Note the data types in the Input Schema-the Snap does not display the SnapLogic-specific syntax in the Input Schema. Here's the same Mapper Snap when you select the Support Type Extensions checkbox. The Snap displays the SnapLogic-specific syntax in the Input Schema.
The input schema in Mapper Snap when you deselect Support Type Extensions checkbox in the JSON Generator Snap is as follows. There is no difference in the preview output of JSON Generator or JSON Parser as the JSON representation remains the same. But the Mapper Snaps downstream of the JSON Generator Snap shows the difference in the Input Schema types. This example Pipeline demonstrates the difference in the input schema types on selecting and deselecting Support Type Extensions checkbox.
Execute only: Performs full execution of the Snap during Pipeline execution does not execute the Snap during Pipeline validation.ĭisabled: Disables the Snap and, by extension, its downstream Snaps.Validate & Execute: Performs limited execution of the Snap (up to 50 records) during Pipeline validation performs full execution of the Snap (unlimited records) during Pipeline execution.For more information, see the Input Schema Types example.
Select this checkbox to enable the Snap to format/parse the Snaplogic-specific syntax indicating objects of the special types, such as byte arrays and date objects in JSON. Optional. Use this property to pass the data in the input document through to the output document and merge it under the key ' original'. The Process array property specifies whether or not the Component should take a root JSON array and write each element of the array as a JSON document. Generate a list of static documents within an array definition which can then be transformed into multiple documents upstream by using a JSON Splitter Snap. Generate static content that produces one output document. The Apache Velocity template can be used to pass dynamic values from upstream Snaps. For more information, see Mock.js is available under the terms of the MIT License.The JSON text is treated as an Apache Velocity template, so you can substitute values from input documents or the pipeline parameters. Is it reproducible after updating to the latest version? What version of Mock.js is the issue reproducible in. Indicate what browsers the issue can be reproduced in. Make sure the problem you're addressing is reproducible.
If you have any questions, please feel free to ask through New Issue. Introduction, mennovanslooten/mockJSON, appendto/jquery-mockjax and victorquinn/chancejs. This library is loosely inspired by Elijah Manor's post Mocking