Size Change: +23 B (0%)

Total Size: 1.44 MB

_{compressed-size-action}

I saw #49464 first, and I left a #49464 (comment) that is very close to the API proposed here. The only difference is that I asked whether copy would make sense as a new transform type. I'm also not entirely sure how pasting is handled, but that's also another place where we could hook in to keep similar functionalities grouped.

Regardless, I like the proposal to offer a way to modify the behavior when copying blocks. It's going to be a useful addition.

A transform is an interesting idea! It feels somewhat ergonomic since you can think of it as a transform from a block to "the clipboard".

Yes I imagine this should affect both duplicating a block and copying a block to the clipboard.

Agree this is a useful proposal especially for extenders. My only hesitation is that if we go with something like #49457 then I'd prefer to have a copy: false block attribute.

Agree this is a useful proposal especially for extenders. My only hesitation is that if we go with something like #49457 then I'd prefer to have a copy: false block attribute.

The idea of copy: false works for me, too. It's a handy shortcut that is less flexible than this one. They could co-exist, too. I really like that you try all those different angles. I need to study better all the use cases you collected in #49466 before I draw any conclusions. What I like about this PR, that you made me think about how we could express all possible block interactions as callbacks to give maximum flexibility.