feat(lib): Updated Generation to EntityModelStreamer... #69
Conversation
…n Jenkins nightly
bvkimball
added
enhancement
…be read via the API
…be read via the API
| case "Timestamp": | ||
| data.properties.push({ | ||
| name: field.fieldName, | ||
| type: "Date", |
There was a problem hiding this comment.
Dates are not actually represented as Date objects in REST - they are returned as the millisecond timestamp, which should be of type number, not Date.
| case "byte[]": | ||
| data.properties.push({ | ||
| name: field.fieldName, | ||
| type: "Strings", |
There was a problem hiding this comment.
The only fields that require the Strings type of string or string[] are fields that start with customText. Configuring a field outside of a custom text field to be a multi-value string array in field maps would be either extremely rare, or a misconfig. For instance, the status string field could be configured to be a multi-value by a customer, but that would break any workflows that rely on status being a single value string. We can add logic that only applies the Strings to fields that are of the format: customText[n]. We don't need to apply this to customTextBlock[n] because those fields should not be configured to be multi-value - they are text areas or html editor blocks.
Probably need to run in Jenkins nightly and do a diff against the results, or open PR if there are changes.