BoxGeometry: Consider Size Array

[ghost]

Consider using key "size" with a size array instead of "xSize", "ySize", "zSize".

[xeolabs]

Yes I was wondering whether I should be doing that - only reason I used the non-array form was for consistency with other scalar properties, for example on XEO.PlaneGeometry, which has properties like xSegments and ySegments (see screenshot from XEO.PlaneGeometry API docs below):

Would be interested though what use cases you've found for having arrays, might be worth breaking that consistency if they're compelling..

[ghost]

I was really comparing to the xyz array of XEO.Transforms. But overall I like using objects and properties better than arrays because they are more descriptive - for example: size.x, segments.x, xyz.x.