Grouping behaviour is hard to discover and understand

[tomwilkie]

This is (my paraphrasing of) feedback from @rade, @squaremo and @awh.

Comments generally include "thats really cool" but "I didn't know to click that small button to make that happen" and "it took a minute for me to figure out what it was doing".

[rade]

Actually, without you explaining what it was doing I would never have figured it out.

[davkal]

Should we just concede defeat and bring the labels back?

[peterbourgon]

Applications   Containers    Hosts  
by name        by image          

[davkal]

Current topos collection object is:

{
    "name": "Applications",
    "url": "/api/topology/applications",
    "grouped_url": "/api/topology/applications-grouped",
    "stats": {
      "node_count": 12,
      "nonpseudo_node_count": 10,
      "edge_count": 13
    }
  }

I propose to nest sub-topologies:

{
    "name": "Applications",
    "url": "/api/topology/applications",
    "stats": {
      "node_count": 12,
      "nonpseudo_node_count": 10,
      "edge_count": 13
    },
    "sub_topologies": [
       {
           "name": "by name",
           "url": "/api/topology/applications-by-name"
       }
   ]
}

[davkal]

FYI, the UI logic uses the last part of the url as the topology ID, e.g. id(/api/topology/applications-by-name) -> applications-by-name so it would be helpful if we can keep this prefix structure.

[davkal]

Fixed via #222