-
-
Notifications
You must be signed in to change notification settings - Fork 143
Remove Event system #433
Comments
Seems like the only places we’re a bit fuzzy on the impact is dcc.Graph and some other dcc components that use the |
I believe what @nicolaskruchten is talking about there falls into two categories:
Anyway these are all possible extensions that occur to me as I'm looking at the current state, not anything that would be lost by removing events and would need replacing. Re: |
All good by me. |
Companion issue to plotly/dash#531
Events are used only lightly in this repo. The changes I see to remove them completely:
Graph
has events, and corresponding properties with the data, for things like click events, hover events... I don't see any need to use the events instead of just letting the property trigger the callback, but folks using the events would need to alter their code. Do we need to add timestamps for these, or is the existence of the data properties enough?A bunch of components expose
change
events, fired with every character typed for example. The underlying value will also trigger a callback, I believe in all of these cases, so I don't think we're losing any functionality, but we may want to add timestamps - to all core components in fact - to help distinguish most-recent-user-input, for cases of multiple parallel ways to update the same output, as described in Remove Event system dash#531Input
already hasn_blur[_timestamp]
andn_submit[_timestamp]
with no corresponding events. It doesn't even have achange
event, but the note above ^^ still may apply to it.Interval
currently fires an event and incrementsn_interval
- so we simply need to remove the event. No timestamp property is provided, would be an easy add if anyone was interested.Textarea
currently exposesblur
andclick
events, which need to be updated to properties.The text was updated successfully, but these errors were encountered: