render: support width/height on shapes

[gavin-ts]

Summary

Support setting width/height on non-image shapes and handles classes/tables with an empty header.

Details

• fixes layout: Make width and height keywords work for non-image shapes #497
• added e2e test with width/height
• width/height can now be set on shapes other than images
• normally shapes are sized at label dimensions + 100 padding, but if the set dimensions are smaller it will only go down to label dimensions + 0 padding as a minimum size
• similarly for classes, sql tables, text and code, as they are rendered at their minimum size already they will only be able to grow in size (see code examples in test below)
• for containers, width and height end up ignored by dagre/elk unfortunately, so this will be a compiler error
• fixes an edge case where an unnamed class would always be sized at 100x100 and added a regression test
• compiler will error if width and height are different on a circle or square shape

e2e test

unnamed class regression test

[alixander]

the main thing here is handling containers. i think width and height only apply to non-containers for now?

[ejulio-ts]

the main thing here is handling containers. i think width and height only apply to non-containers for now?

makes sense as TALA doesn't take it under consideration for proper placement.
In this case, should we add an error/warning to the compiler?
Similarly, if the set width/height is smaller than the label requirement, should we warn the user as they might get a wrong idea of the sizing if based on a relative size that we didn't as they expected

[gavin-ts]

the main thing here is handling containers. i think width and height only apply to non-containers for now?

makes sense as TALA doesn't take it under consideration for proper placement. In this case, should we add an error/warning to the compiler? Similarly, if the set width/height is smaller than the label requirement, should we warn the user as they might get a wrong idea of the sizing if based on a relative size that we didn't as they expected

I think we could add a compiler warning for setting width or height on a container, but do we have currently have non-error warnings?

I don't think setting the width or height to a value smaller than the minimum size should be a compiler warning, I think should just be the described behavior in the documentation.

[alixander]

I think we could add a compiler warning for setting width or height on a container, but do we have currently have non-error warnings?

sounds nice but in practice it'd be annoying, because the container changes depending on layout. so from one compile to the next, the warning appears unpredictably

[gavin-ts]

I think we could add a compiler warning for setting width or height on a container, but do we have currently have non-error warnings?

sounds nice but in practice it'd be annoying, because the container changes depending on layout. so from one compile to the next, the warning appears unpredictably

The container structure should be the same regardless of layout, I think @ejulio-ts means always warning if you define width on a container shape, regardless of the value.

[ejulio-ts]

yeah, for containers once you set, you get the error/warning.
for other shapes, if there's a size mismatch, the same (basically, for containers we assume it is always a mismatch)

[ejulio-ts]

non-container shapes

Maybe, non-container objects as there're no such thing as container shapes

[alixander]

i wanted to call every "node" a shape, as object is pretty all-encompassing. but i'm not 100% sure about that route

[ejulio-ts]

well, from a changeling perspective, shape reminds me of shape keyword and not the objects themselves

[gavin-ts]

from https://d2lang.com/tour/containers :

server
# Declares a shape inside of another shape
server.process