consul/ui/packages/consul-ui
John Cowen 9eab715149
ui: Move all our icons to use CSS custom properties instead of SASS vars (#10298)
* ui: Move all our icons to use CSS custom properties

The good thing about SASS vars is, if you don't use them they get removed from the final build. Whereas with CSS we have no tree-shaking to get rid of unused CSS custom properties. We can mostly work around this and for some things like colors its no big deal if we have some hex-codes in the build that we don't use as hex-codes are relatively small.

We've been slowly but surely moving all of our colors (and other things) to use CSS custom properties instead of SASS vars now that we have them available.

This commit makes use of the 'tree-shaking' abilities of @extend to ensure that we only compile in the icons that we use.

This commit is mostly churn-less as we already use @extend for the majority of our icons, so generally there is zero change here for working on the UI, but I did spot one single place where we were using SASS vars instead of @extend. This now uses the new form (second commit)

Interestingly this reduces our CSS payload by ~2kb to ~53kb (around 25kb of that is these icons)
2021-06-21 11:54:58 +01:00
..
app ui: Move all our icons to use CSS custom properties instead of SASS vars (#10298) 2021-06-21 11:54:58 +01:00
blueprints ui: Update project blueprints for native classes (#9775) 2021-02-24 09:03:18 +00:00
config ui: Support Route optional parameters/segments (#10212) 2021-05-26 17:43:46 +01:00
docs ui: Adds QUnit toggle bookmarklet to our docs (#10269) 2021-05-20 16:24:50 +01:00
lib ui: Loader amends/improvements (#10181) 2021-05-07 12:23:29 +01:00
mock-api ui: Unix Domain Socket support (#10287) 2021-05-26 17:52:25 +01:00
node-tests/config ui: Add Admin Partition feature flag (#10051) 2021-04-22 12:22:40 +01:00
public Update brand assets (#10081) 2021-05-03 16:19:09 +01:00
server ui: CSP Improvements (#9847) 2021-03-17 10:46:21 +00:00
tests ui: Support Route optional parameters/segments (#10212) 2021-05-26 17:43:46 +01:00
translations ui: Create and use collapsible notices component (#10270) 2021-05-25 11:02:38 -04:00
vendor ui: CSP Improvements (#9847) 2021-03-17 10:46:21 +00:00
.dev.eslintrc.js
.docfy-config.js ui: Improves UI engineering docs (#9875) 2021-03-17 15:58:17 +00:00
.editorconfig
.ember-cli ui: Default to glimmer components (#9121) 2020-11-06 14:54:44 +00:00
.eslintignore ui: Move linting to the `node:test` script (#9385) 2020-12-14 15:28:35 +00:00
.eslintrc.js ui: Remove storybook, add docfy (#9831) 2021-03-08 12:22:01 +00:00
.istanbul.yml
.nvmrc ui: Bump node to v14 (#10238) 2021-05-18 16:30:19 +01:00
.prettierrc
.template-lintrc.js ui: Search/filtering 'Filtered by:' search status (#9442) 2021-01-25 18:13:54 +00:00
.watchmanconfig
GNUmakefile ui: Move linting to the `node:test` script (#9385) 2020-12-14 15:28:35 +00:00
README.md ui: Add Admin Partition feature flag (#10051) 2021-04-22 12:22:40 +01:00
ember-cli-build.js ui: Use babel plugin to strip calls to runInDebug (#10237) 2021-05-17 13:27:34 +01:00
package.json ui: Fixup prettier for scss files and run (#10296) 2021-05-27 13:23:54 +01:00
testem.js ui: Add an optional environment variable to control how testem starts (#9793) 2021-02-22 14:53:05 +00:00

README.md

consul-ui

Prerequisites

You will need the following things properly installed on your computer.

Installation

  • git clone https://github.com/hashicorp/consul.git this repository
  • cd ui/packages/consul-ui
  • make start or yarn && yarn start

Yarn Commands

Most used tooling scripts below primarily use make which will yarn install and in turn call node package scripts.

List of available project commands. yarn run <command-name>

Command Description
build:staging Builds the UI in staging mode (ready for PR preview site).
build:ci Builds the UI for CI.
build Builds the UI for production.
lint Runs all lint commands.
lint:hbs Lints hbs template files.
lint:js Lints js files.
format Runs all auto-formatters.
format:js Auto-formats js files using Prettier.
format:sass Auto-formats scss files using Prettier.
start Runs the development app on a local server using the mock API.
start:consul Runs the development app local server using a real consul instance as the backend.
start:staging Runs the staging app local server.
test Runs the ember tests in a headless browser.
test:view Runs the ember tests in a non-headless browser.
test:oss Runs only the OSS ember tests in a headless browser.
test:oss:view Runs only the OSS ember tests in a non-headless browser.
test:coverage:view Runs only the test specified for coverage in a non-headless browser.
test:node Runs tests that can't be run in ember using node.
doc:toc Automatically generates a table of contents for this README file.

Running / Development

The source code comes with a small development mode that runs enough of the consul API as a set of mocks/fixtures to be able to run the UI without having to run consul.

You can also run the UI against a normal Consul installation.

  • consul server -dev to start consul listening on http://localhost:8500
  • make start-consul to start the ember app proxying to consul (this will respect the CONSUL_HTTP_ADDR environment variable to locate the Consul installation.
  • Visit your app at http://localhost:4200.

Example:

CONSUL_HTTP_ADDR=http://10.0.0.1:8500 make start-consul

Environment Variables

There are various environment variable you can use whilst running make start or make test to configure various features:

Variable Default Value Description
TESTEM_AUTOLAUNCH Chrome Controls which browser to open tests in. A setting of "" means 'let me manually open the browser'
EMBER_TEST_REPORT Output a test report

Contributing/Engineering Documentation

We have an in-app (only during development) component storybook and documentation site which can be visited using the Eng Docs link in the top navigation of the UI.

Browser 'Debug Utility' Functions and 'Environment' Variables

Run make start then visit http://localhost:4200/ui/docs/bookmarklets for a list of debug/engineering utilities you can use to help development of the UI under certain scenarios.

Code Generators

Many classes used in the UI can be generated with ember generators, try ember help generate for more details

Running Tests

Tests use the mock api (see ./mock-api for details)

  • make test or yarn run test
  • make test-view or yarn run test:view to view the tests running in Chrome

OSS only tests can also be run using:

  • make test-oss or yarn run test:oss
  • make test-oss-view or yarn run test:oss:view to view the tests running in Chrome

Linting

make lint currently runs linting on the majority of js files and hbs files (using ember-template-lint).

See .eslintrc.js and .eslintignore for specific configuration.

Building

  • make build builds the UI for production usage (env=production)
  • make build-ci builds the UI for CI/test usage (env=test)

Static files are built into ./dist

Running Tests in Parallel

Alternatively, ember-exam can be used to split the tests across multiple browser instances for faster results. Most options are the same as ember test. To see a full list of options, run ember exam --help.

Note: The EMBER_EXAM_PARALLEL environment variable must be set to override the default parallel value of 1 browser instance in testem.js.

To quickly run the tests across 4 parallel browser instances:

make test-parallel

To run manually:

$ EMBER_EXAM_PARALLEL=true ./node_modules/.bin/ember exam --split <num> --parallel

More ways to split tests can be found in the ember-exam README.md.