* Adjust Firefox zoom sensitivity.
* Animate zooming to make it appear smoother (especially on Firefox).
* Debounced zoom tracking.
* Addressed the comments.
* Experimental.
* Getting somewhere.
* Good zooming behaviour.
* Working timeline zooming & panning.
* Clickable timestamps.
* Dragging cursor
* Timeline panning buttons.
* Capping at current time.
* Scale limits.
* Better ticks.
* Time tags fading in smoothly.
* Removed seconds.
* Better tick spacing.
* Vertical panning as zooming.
* Organizing the code..
* Replaced d3-zoom with native events.
* Got rid of scaleX
* More code beautified.
* Almost done polishing the code.
* Some cleanup.
* Better request triggers.
* More cleaning up.
* Styled the timestamp input.
* Final cleanup.
* Update yarn.lock
* Zoom tracking.
* Animate timeline translations.
* Fixed the PAUSE button glitch and updating the time control info.
* Opacity fix and timeline arrows removed.
* Fixed the red vertical bar.
* Use preventDefault() on timeline scrolling.
* Made Resource view nodes clickable.
* Remove selection when clicking on the background.
* Use opacity instead of the blue overlay for selected nodes.
When the scope-app restarts, it no longer has a
reference to the previous node set. Therefore,
the delta update adds *all* nodes but does not
remove legacy ones.
`reset==true` tells the frontend to start fresh.
Fixes#2708
If the scope-app API unexpectedly restarts, it has no report
at hand (until it gets one from the probe) and sends node
count 0 to the frontend for all topologies. Once the report
arrives, it will send the proper count.
What happened was the frontend did hide Processes for a short
time till the node count recovered. This moved the topology
selection to the always visible Containers (hide_if_empty == false)
while keeping the graph as is.
Once the node count recovers, Processes comes back but the
selection is still at Containers.
We now keep the selected topology visible at all time even if
the API returns a node count of 0. This recovers nicely when
the correct node counts come in. Once the user selects a different
topology while and a backend response arrives, it disappears.
Fixes#2646
The package version is irrelevant for the build process
and is not read anywhere.
The package is not published and causes confusion if the
bump is forgotten.
* Initial top level control.
* Added the jump buttons.
* Tiny styling adjustments.
* Massive renaming.
* Pause info
* Added slider marks.
* Improved messaging.
* Freeze all updates when paused.
* Repositioned for Configure button.
* Improved the flow.
* Working browsing through slider.
* Small styling.
* Hide time travel button behind the feature flag.
* Fixed actions.
* Elements positioning corner cases.
* Removed nodes delta buffering code.
* Fixed the flow.
* Fixed almost all API call cases.
* Final touches
* Fixed the tests.
* Fix resource view updates when time travelling.
* Added some comments.
* Addressed some of @foot's comments.
While we're there, adopt a consistent ordering for all places that shapes are listed
Order is least sides to most sides, with circle before polygons, and complex shapes (currently just Cloud) after.
On shape choices for topologies:
* Since the k8s logo is a heptagon, we want pods to be heptagons.
* Since triangle is 'a bit weird', we put it on the least-important type, replica sets.
* Pentagons look a little weirder than octogons (it's the lack of symmetry) so we put octogons on the most common (deployments)
