10 Commits

Author	SHA1	Message	Date
hashicorp-copywrite[bot]	a9d61ea3fd	Update copyright file headers to BUSL-1.1	2023-08-10 17:27:29 -05:00
hashicorp-copywrite[bot]	f005448366	[COMPLIANCE] Add Copyright and License Headers	2023-04-10 15:36:59 +00:00
Luiz Aoqui	551e3940ca	ui: upgrade sass 1.32.6 -> 1.43.4	2021-11-05 18:09:19 -04:00
Michael Lange	2e2bcc50a7	Add an animation for the initializing state	2020-01-31 12:56:11 -08:00
Michael Lange	e95370464a	Redo the node-status-light CSS to be icon-based	2020-01-31 12:56:08 -08:00
Michael Lange	2f1dec2924	Allow for an icon within the node status light	2020-01-31 12:55:55 -08:00
Michael Lange	3ad898762b	Reformat the client detail page to use the two-row header design	2020-01-23 16:34:11 -08:00
Buck Doyle	83d92251c5	UI: Fix client sorting (#6817) ... There are two changes here, and some caveats/commentary: 1. The “State“ table column was actually sorting only by status. The state was not an actual property, just something calculated in each client row, as a product of status, isEligible, and isDraining. This PR adds isDraining as a component of compositeState so it can be used for sorting. 2. The Sortable mixin declares dependent keys that cause the sort to be live-updating, but only if the members of the array change, such as if a new client is added, but not if any of the sortable properties change. This PR adds a SortableFactory function that generates a mixin whose listSorted computed property includes dependent keys for the sortable properties, so the table will live-update if any of the sortable properties change, not just the array members. There’s a warning if you use SortableFactory without dependent keys and via the original Sortable interface, so we can eventually migrate away from it.	2019-12-12 13:06:54 -06:00
Michael Lange	bb855b5f21	Add ineligibility to the status light	2018-05-30 11:27:21 -07:00
Alex Dadgar	ddc2efa4ac	sync	2017-09-19 10:08:23 -05:00