-
Notifications
You must be signed in to change notification settings - Fork 11
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
Display Query name per each timeline entry #395
Comments
Hey @dcaldastp, thanks for the suggestion! How would you feel about being able to see the query name when hovering over the |
Hey @andyrichardson, thanks for the quick reply. Honestly, hover would not be as helpful since I would like to look at the timeline as a whole without having to keep track of a mental map of the timeline position to query/mutation name (I'm looking at a timeline with 20+ queries, it becomes a bit hard to keep track of it, even with the hover). |
Thanks for explaining your reasoning - that does make a lot of sense! For the time being, I think tool-tips would be the best we can do with the current layout due to the lack of space. I did have a mess around with an alternative layout (below) - might make it easier to distinguish and find queries but would take more time than I have available to implement. Maybe something for the future 🤞 |
I like your thinking, although for information heirarchy, I think this might be a little tricky. The whole "row" is the query and ideally the name would be associated with the row rather than a "duration". There are also some additional situations where this might not quite work:
|
About
Here's a sketch of the required addition - see
myQueryX
written in read near theQ
icon, this is just a suggestion of course, placement of the label could be some other more suitable place.Each entry in the timeline would have somewhere displayed the query name for better exploration. This will save us the effort of clicking each entry to figure out which query we're looking at, which IMO carries an additional obstacle for the developer trying to wrap their head around the timeline.
The text was updated successfully, but these errors were encountered: