Allow objects without braces around them inside arrays about config

[havocp]

It is an interesting idea. Would have to play with the parser and see if it's workable. It creates some ambiguity; note that outside of [], "a=1, b=2" is a single object, but here "a=1,b=1" would be two objects in a list. Also it requires the parser to "look ahead" because in all existing cases, if you see "alpha" in "alpha=1" you know that "alpha" is an object key already. But in this case, you don't know whether "alpha" is an object key or just a string, until you get to the "=" or ":" - so that's a look-ahead to the next token that is never (if I remember right) currently done. Anyway those are just some possible issues I thought of offhand, it would need more digging in.

[pditommaso]

I don't think that it will create an ambiguity, on the contrary in my opinion it would be even more coherent with the JSON array semantic. In fact an array can hold a list of primitive types or objects, so the assignment notation can only represent an object since it is not a primitive types.

My real use case it the following: I have a list of components, for each of them I have to provide a configuration. I know that I could use the object notation instead of the array, for example:

components { alpha: { a:1, b:2 }, beta: { x:3, y:4} } 

But the main problem with this approach is that I cannot have different configuration for the same "component" because the last will override the previous ones. So here, the array is the best choice:

components [ {alpha: { a:1, b:2 }}, {beta: { x:3, y:4}}, {beta: { x:5, y:6}} ]  

But the syntax it is not so clean as it would be expected. Much better would be:

components [ alpha = { a:1, b:2 }, beta = { x:3, y:4 }, beta = { x:5, y:6 } ]   

[ericacm]

+1