Setting position in Shape.Rectangle constructor causes incorrect bounds calculations

[nikkwong]

var shape1 = new Shape.Rectangle({
        point: [20, 20],
        size: new paper.Size(100, 100),
        fillColor: 'blue'
});

const shape2 = new Shape.Rectangle({
        fillColor: 'red',
        position:  shape1.position,
        size: new paper.Size(50, 50)
})

console.log(shape1.bounds.area) // 10000
console.log(shape2.bounds.area) // 0

Sketch

[nikkwong]

Somewhat unrelated but also wonder why you can't just copy bounds from one item to the other.

var shape1 = new Shape.Rectangle({
        size: new paper.Size(100, 100),
        fillColor: 'blue'
});

const shape2 = new Shape.Rectangle({
        fillColor: 'red',
        bounds:  shape1.bounds
})

console.log(shape1.bounds.area) // 10000
console.log(shape2.bounds.area) // 0

If bounds is supposed to be readonly, it would be nice to note that somewhere.

[sasensi]

@nikkwong, thank you for the report.
The bug was actually linked to the fact that position was set before size, resulting in invalid bounds being cached. #1708 will fix it.

About your second statement, yes, I think that bounds are supposed to be readonly and we are working on improving the readonly states in the documentation along with the typescript documentation improvement.
@lehni, can you confirm that every variant of bounds (bounds, strokeBounds, ...) should be marked as readonly ? If yes, I can make a PR to fix the documentation.