Filip Barl

For example by adding a boolean flag option. * For users who know they want to use a fixed version and not get distracted by the upgrades * For demo...

#### Background Currently, there is a piece of logic in the code which redirects Graph View -> Table View initially if the graph is estimated to be _too big_. It's...

Highlight the search query matches in table view

5

To make the search behaviour consistent between Graph and Table views, we should probably highlight the matches based on the search query in both views. Pinned terms could still be...

Now that the edge component has been moved into the shared repo, we should replace the Scope component with the one from there - https://github.com/weaveworks/ui-components/pull/299. Related to #3261.

 From https://github.com/weaveworks/scope/pull/2353#issuecomment-288378894 > I'd prefer a show-more link, that visibly expands the container, somehow carries a number of entries, and thereby makes it easy to deduce how many items...

The hash `nodeSummaryGroupSpecs` in `render/detailed/node.go` contains column descriptions that are (always?) duplicated in `probe/*/reporter.go`. As @paulbellamy suggested, we could instead make `NodeSummaryGroup.Columns` just an ordered list of keys referring to...

Motivated by https://github.com/weaveworks/ui-components/issues/492#issuecomment-559455533. Adding a _How to Contribute_ section would probably be a good start.

It doesn't feel right that this modular components repo also contains global styles that we're implicitly expecting the end user to import. The remaining global styles here consist of: *...

These components would probably be most important to cover: * `DataTable` * `ResourceDial` * `PrometheusGraph` * `TimeTravel`

The `ResourceDial` component currently expects an internal `react-route` link in the `to` prop, so it can't link to any external URLs.