Justin Fagnani

Hey @TarunavBA we have an agency that produces our assets for us. @graynorton is going to forward this to them.

What we would need out of a decorator or other solution is a way to turn an event into a "payload". A property name would usually suffice, but a callback...

This is a good thing for us to do to match the behavior of React 19's WC support.

We're thinking about this one. It's a decent helper, but also very easy, and we need to figure out where to put it.

I'm a bit hesitant to add more lifecycle callbacks right now in general, as we see what we need for more SSR cases. Already you can do: ```ts willUpdate() {...

To match the behavior of https://github.com/facebook/react/pull/24541 I think we _don't_ need an allowlist of boolean attribute names. The allowlist won't work for custom boolean attributes anyway. What we should do...

@kevinpschaaf was actually working on this at one point, and I think hit some problems that made it not worth it. Maybe he can recall what it was.

Does this matter anymore?

@sorvell could we get this broken up into separate PRs per decorator?

I don't see any problems in the code there. I think this might be a TypeScript bug.