Thank you for your feedback. We believe this feature request makes sense. Previously, we did not implement it due to significant performance overhead and memory leaks. However, if users truly need it, we should find a way to enable it on-demand (or have it disabled by default and allow users to enable it manually).

I would also find the component events timeline very useful. I agree that making it an on-demand, or configurable option makes sense.

It would be really useful to have it at least as an option to activate it momentarily. I am currently working on a bug that would make it much easier to see the events emitted.

Cooking 🧑‍🍳

See you soon 😊

See you soon 😊

Nice!

Great! 👍🏻

@webfansplz Looks really great! However, am I the only one expecting the "Enabled"/"Disabled" toggle to say the reverse of what they do currently?

@webfansplz Looks really great! However, am I the only one expecting the "Enabled"/"Disabled" toggle to say the reverse of what they do currently?

A classic, and partly philosophical question; should the text indicate the current state or should it indicate what happens when you click? In my opinion, it partly depends on what kind of UI component it is, and partly on how the text is formulated (if it makes it clear whether it is state or action that is meant).

In general, I probably prefer that the text on a button refers to the action taken when clicked, but that's not a strong opinion.

Agreed – the current text is neither showing active state nor action, it's showing state if clicked 😄

Thanks for the feedback, I've submitted a PR to improve the UX about it.

This still leaves room for confusion. I propose #642.