Closed bpauli closed 11 years ago
In this case, you can always use the TypeHint as a property in the .json file. You don't have to force it in the task itself.
I agree that this hardcoded TypeHint is suboptimal.
But currently
{
"categories": ["jquery"]
}
and
{
"categories": "jquery"
}
produce the same property in the JCR and this is IMO wrong. An array should be always a multi-value field. So I guess the hardcoded TypeHit will be the lesser of the two evils
My latest commit should fix this problem. Unless the user specifies a TypeHint
inside the .json
file, the task automatically adds one with value String[]
.
Great, Thank you!
I close the issue.
When a value is an array the type of the property should always be an array. even when only one element is in the array.