Open aiwilliams opened 3 years ago
@erkangz would you please elaborate on the reason for calling camelCase()
on fields? It seems to me that we should support spaces in names as well as +
characters, perhaps others?
The workaround is to obtain the custom field ID.
@erkangz would you please elaborate on the reason for calling
camelCase()
on fields? It seems to me that we should support spaces in names as well as+
characters, perhaps others?
I don't think it's necessary for camelCase()
in this scenario. Perhaps this is for making standard fields like Description
to description
when added to the entity?
It has been reported that custom fields with a
+
character in the name are not ingested.The user configures (in the UI) a
customFields
value (name or id, comma separated) that is validated by the following code:Perhaps the
camelCase()
function is the culprit here.Change the code to support a
+
character while maintaining whatever was supported by assuming that fields should be madecamelCase()
.