Closed cab938 closed 10 months ago
Added @soney , Steve can you comment and share thoughts? I've been mulling this over and I'm unsure whether this makes sense to include in the base telemetry package. It feels like it is a more specialized need to me, but maybe not. Shall we discuss here?
For this cellEditEvent, should we log data 1) for every keystroke, 2) or when the edit operation type changes (e.g. from write to delete, from delete to write), 3) or repeatedly based on a short time interval (e.g. 0.5 seconds) during the user's continuous editing process?
One reasonable? way to do this is to log codemirror events with a custom producer which could be included in the base install if it made sense.
I'm not sure if this makes sense, but I think Steve does. It might make more sense to me to build this as another extension and then wrap the two of them together. I'm unsure of the general need to log at such a fine level, and it does start to tie the impl to not just jupyter but now code mirror.
Regardless, I think building out the code for this is great, and even if it were in another extension it would be a great example of how to build code to use the telemetry pathways.