17f10ffd0d
* ui: Add tab navigation to the browser history/URLs
This commit changes all our tabbed UI interfaces in the catalog to use
actual URL changes rather than only updating the content in the page
using CSS.
Originally we had decided not to add tab clicks into the browser
history for a variety of reasons. As the UI has progressed these tabs
are a fairly common pattern we are using and as the UI grows and
stabilizes around certain UX patterns we've decided to make these tabs
'URL changing'.
Pros:
- Deeplinking
- Potentially smaller Route files with a more concentrated scope of the
contents of a tab rather than the entire page.
- Tab clicks now go into your history meaning backwards and forwards
buttons take you through the tabs not just the pages.
- The majority of our partials are now fully fledged templates (Octane
🎉)
Cons:
- Tab clicks now go into your history meaning backwards and forwards
buttons take you through the tabs not just the pages. (Could be good and
bad from a UX perspective)
- Many more Route and Controller files (yet as mentioned above each of these
have a more reduced scope)
- Moving around the contents of these tabs, or changing the visual names
of them means updates to the URL structure, which then should
potentially entail redirects, therefore what things that seem like
straightforwards design reorganizations are now a little more impactful.
It was getting to the point that the Pros outweight the Cons
Apart from moving some files around we made a few more tiny tweaks to
get this all working:
- Our freetext-filter component now performs the initial search rather
than this happening in the Controller (remove of the search method in
the Controllers and the new didInsertElement hook in the component)
- All of the <TabNav>'s were changed to use its alternative href
approach.
- <TabPanel>s usage was mostly removed. This is th thing I dislike the
most. I think this needs removing, but I'd also like to remove the HTML
it creates. You'll see that every new page is wrappe din the HTML for
the old <TabPanel>, this is to continue to use the same HTML structure
and id's as before to avoid making further changes to any CSS that might
use this and being able to target things during testing. We could have
also removed these here, but it would have meant a much larger changeset
and can just as easily be done at a later date.
- We made a new `tabgroup` page-object component, which is almost
identical to the previous `radiogroup` one and injected that instead
where needed during testing.
* Make sure we pick up indexed routes when nspaces are enabled
* Move session invalidation to the child (session) route
* Revert back to not using didInsertElement for updating the searching
This adds a way for the searchable to remember the last search result
instead, which changes less and stick to the previous method of
searching.
108 lines
2.9 KiB
Gherkin
108 lines
2.9 KiB
Gherkin
@setupApplicationTest
|
|
Feature: dc / services / show: Show Service
|
|
Scenario: Given a service with an external source, the logo is displayed
|
|
Given 1 datacenter model with the value "dc1"
|
|
And 1 node models
|
|
And 1 service model from yaml
|
|
---
|
|
- Service:
|
|
Tags: ['Tag1', 'Tag2']
|
|
Meta:
|
|
external-source: consul
|
|
---
|
|
When I visit the service page for yaml
|
|
---
|
|
dc: dc1
|
|
service: service-0
|
|
---
|
|
Then I see externalSource like "consul"
|
|
And the title should be "service-0 - Consul"
|
|
|
|
Scenario: Given a service with an 'unsupported' external source, there is no logo
|
|
Given 1 datacenter model with the value "dc1"
|
|
And 1 node models
|
|
And 1 service model from yaml
|
|
---
|
|
- Service:
|
|
Tags: ['Tag1', 'Tag2']
|
|
Meta:
|
|
external-source: 'not-supported'
|
|
---
|
|
When I visit the service page for yaml
|
|
---
|
|
dc: dc1
|
|
service: service-0
|
|
---
|
|
Then I don't see externalSource
|
|
Scenario: Given various services with various tags, all tags are displayed
|
|
Given 1 datacenter model with the value "dc1"
|
|
And 3 node models
|
|
And 1 service model from yaml
|
|
---
|
|
- Service:
|
|
Tags: ['Tag1', 'Tag2']
|
|
- Service:
|
|
Tags: ['Tag3', 'Tag1']
|
|
- Service:
|
|
Tags: ['Tag2', 'Tag3']
|
|
---
|
|
When I visit the service page for yaml
|
|
---
|
|
dc: dc1
|
|
service: service-0
|
|
---
|
|
And I click tags on the tabs
|
|
Then I see the text "Tag1" in "[data-test-tags] span:nth-child(1)"
|
|
Then I see the text "Tag2" in "[data-test-tags] span:nth-child(2)"
|
|
Then I see the text "Tag3" in "[data-test-tags] span:nth-child(3)"
|
|
Scenario: Given various services the various nodes on their instances are displayed
|
|
Given 1 datacenter model with the value "dc1"
|
|
And 3 node models
|
|
And 1 service model from yaml
|
|
---
|
|
- Checks:
|
|
- Status: passing
|
|
Service:
|
|
ID: passing-service-8080
|
|
Port: 8080
|
|
Address: 1.1.1.1
|
|
Node:
|
|
Address: 1.2.2.2
|
|
- Service:
|
|
ID: service-8000
|
|
Port: 8000
|
|
Address: 2.2.2.2
|
|
Node:
|
|
Address: 2.3.3.3
|
|
- Service:
|
|
ID: service-8888
|
|
Port: 8888
|
|
Address: 3.3.3.3
|
|
Node:
|
|
Address: 3.4.4.4
|
|
---
|
|
When I visit the service page for yaml
|
|
---
|
|
dc: dc1
|
|
service: service-0
|
|
---
|
|
Then I see address on the instances like yaml
|
|
---
|
|
- "1.1.1.1:8080"
|
|
- "2.2.2.2:8000"
|
|
- "3.3.3.3:8888"
|
|
---
|
|
Scenario: Given a dashboard template has been set
|
|
Given 1 datacenter model with the value "dc1"
|
|
And settings from yaml
|
|
---
|
|
consul:urls:
|
|
service: https://consul.io?service-name={{Service.Name}}&dc={{Datacenter}}
|
|
---
|
|
When I visit the service page for yaml
|
|
---
|
|
dc: dc1
|
|
service: service-0
|
|
---
|
|
And I see href on the dashboardAnchor like "https://consul.io?service-name=service-0&dc=dc1"
|