Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Decide what should show up on time widget, and when #4220

Closed
teh-cmc opened this issue Nov 14, 2023 · 0 comments · Fixed by #6586
Closed

Decide what should show up on time widget, and when #4220

teh-cmc opened this issue Nov 14, 2023 · 0 comments · Fixed by #6586
Assignees
Labels
🔩 data model 💬 discussion ui concerns graphical user interface

Comments

@teh-cmc
Copy link
Member

teh-cmc commented Nov 14, 2023

The time widget currently doesn't display InstanceKeys, whether they were logged explicitly or auto-generated by the DataStore.
On the other hand, we always mention them when selecting a component, which is no doubt confusing to users.

image (19)

  • Should explicitly logged InstanceKeys show up?
  • What about auto-generated ones?
  • What about cascading side-effects such as empty batches logged by pending clears?
  • What about indicators?
  • Should the time widget be a faithful representation of the data model ("if it gets returned by a query, then it shows up here")?
  • Etc

There is also the notion of "what is an event?": we currently display a "number of events" that corresponds to the number of raw components logged at this point in time. Should we show the number of rows instead, i.e. the number of log calls?

@teh-cmc teh-cmc added 💬 discussion ui concerns graphical user interface 🔩 data model labels Nov 14, 2023
@teh-cmc teh-cmc self-assigned this Mar 15, 2024
@teh-cmc teh-cmc closed this as completed in 176b937 Jul 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🔩 data model 💬 discussion ui concerns graphical user interface
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant