The row height feature is a great first step, but the way it works is quite surprising.
I suspect that in the vast majority of use cases, users need to set a maximum height to prevent rows from growing too much. Instead, this feature sets a fixed height on all rows, whether they need the space or not, making it practically useless for any value > 1. I’m very curious what the driving use cases were, which needed all their rows be 2 or 3 lines tall? I don’t think I’ve ever come across one, whereas I’ve needed a max row height in almost every nontrivial table I have ever created.
Additionally — and this is more controversial — I would question whether this should really be a property of the table. I would argue that a column property is at least as useful, if not more: some columns contain essential data (e.g. name), and it’s fine for them to stretch out the row more because seeing the whole value is more improtant. Others are more tangential (e.g. notes) and can be truncated. Perhaps the north star UI is a max row height setting per column and a fallback one for the whole table.