CustomElement supports declarative initialization of properties that are arrays of strings. However, the inline comment says to separate array elements with commas whereas the code looks for spaces.
Change the code to match the comment and old dijit behavior, i.e.:
<my-fancy-element myObj="[1,2,3,'string with commas ,,,']">
@cc brunano21
PS: I traced the array parsing code back to 731e67c877458f812bdcf6b17e38e43daa738823 but it's unclear if I was doing spaces instead of commas intentionally or not. The argument for spaces is that that's how CSS class works.
CustomElement supports declarative initialization of properties that are arrays of strings. However, the inline comment says to separate array elements with commas whereas the code looks for spaces.
Change the code to match the comment and old dijit behavior, i.e.:
and then:
For other situations, such strings containing commas or arrays of numbers, code must use the JSON conversion on generic objects, i.e.:
and then:
@cc brunano21
PS: I traced the array parsing code back to 731e67c877458f812bdcf6b17e38e43daa738823 but it's unclear if I was doing spaces instead of commas intentionally or not. The argument for spaces is that that's how CSS
class
works.