When viewing a run in Nextmv Console, there is a size limit for rendering the input and output for the run. If an input or output file is above this threshold, rather than rendering a visual or the contents of the JSON file, an interface for downloading the file is displayed.
However, sometimes an input’s large file size is because of “machine” data included in the file, and the amount of information that is of interest to an operator or developer is within Console’s file display threshold.
To accommodate this scenario, a new feature has been added to Nextmv Console that trims machine-oriented properties from the input file when viewing a run. After the properties have been trimmed, if the run’s updated input file size is within the display thresholds then the input will be re-rendered with the appropriate display (e.g. a mapping visual if it’s a routing app).
At the moment there are two properties that are trimmed from the input file:
If these input properties do not exist no action is taken. Also, if one or more of these properties are trimmed, but the input file size still remains above the rendering threshold, the download input interface will remain as is.
Note that the input is modified in the browser session on the front-end only. The backend data remains as is and cannot be modified. Also, you can always download the input file via the download interface to see its full contents.
