Feature Request: clickData Timestamp

[SterlingButters]

Just read this super in-detail Gist on comparing the clickData property amongst multiple components: https://gist.github.com/shawkinsl/22a0f4e0bf519330b92b7e99b3cfee8a

I found myself in need of this too so I thought I'd suggest a timestamp key in clickData

[alexcjohnson]

Have you seen dash.callback_context #608? We're hoping this alleviates the need for all of these timestamp properties.

[SterlingButters]

No I hadn't seen that! Checking it out now!

Does

Just merged, going into next release.

mean dash 0.40.0?

[alexcjohnson]

In fact it's been released since v0.38
https://github.com/plotly/dash/blob/v0.39.0/CHANGELOG.md#added-1

[SterlingButters]

I see, so eventually the timestamps for all inputs will be implemented through the callback_context? Because right now

trigger = dash.callback_context.triggered[0]
print(trigger)

returns data that I could still retreive from properties

{'prop_id': 'assembly-graph.clickData', 'value': {'points': [{'curveNumber': 0, 'x': 2, 'y': 10, 'z': 1, 'text': 'Test'}]}}

[alexcjohnson]

No, the idea of triggered is that if you’re using timestamps (or diffing) to determine which input changed, why don’t we just tell you which one changed? If it’s in triggered, it’s the reason the callback fired. Did you have a different usage of timestamp?

[SterlingButters]

Brilliant, it makes perfect sense now that you put it like that. This will work perfectly, indeed, thanks!