-
-
Notifications
You must be signed in to change notification settings - Fork 144
Remove _timestamp properties, or fix & standardize? #467
Comments
We have a better solution to this - which has already been merged and will be in the next release: callback context, that directly tells you which input(s) triggered the call plotly/dash#608 Having mismatched behavior for these is definitely a problem, but the solution - if callback context takes care of every case people were using |
Dash 0.38 is released including |
The current proposal is to deprecate - and eventually remove - all |
Sounds great. In my use of dash, I only use |
Hello,
A minor problem appeared when using an
Input
component. Then_submit_timestamp
property returns a string (e.g.'2019-02-23T16:39:12.076Z'
) while other components such as Button returns an int (e.g.1550939942322
).I often use the following command to find out which button was last pressed and I can't use it with
Input
:Maybe you should standardize the two outputs.
The text was updated successfully, but these errors were encountered: