@brightspace-ui/core

core

A collection of core UI components.

Installation

To install from NPM:

npm install @brightspace-ui/core

Components

• Buttons: normal, primary, icon and subtle buttons
• Colors: color palette
• Icons: iconography SVGs and web components
• Meter: linear, radial, circle meter web components.
• More/less: constrain long bits of content
• Typography: typography styles and components

Helpers

• Helpers: helpers for composed DOM, unique ids, etc.

Mixins

• Mixins: mixins for localization, RTL styles, etc.

Usage

Structure

/components/ - Web components for use in your composite components or application (ex. buttons, links, etc)

/helpers/ - Helpers for use in your web components or mixins (ex. composed DOM helpers)

/mixins/ - Mixins for use in your web components (ex. localize, RTL, etc)

/test/ - Index and shared styles for unit tests

/tools/ - Development tools for building, testing, etc.

Developing, Testing and Contributing

After cloning the repo, run npm install to install dependencies.

Run npm run build once, or any time icon or language files are changed.

If you don't have it already, install the Polymer CLI globally:

npm install -g polymer-cli

Running the demos

To start a local web server that hosts the demo page and tests:

polymer serve

Testing

To lint:

npm run lint

To run visual-diff tests:

npm run test:diff

To run a subset of visual-diff tests:

npm run test:diff -- -g some-pattern

To update visual-diff goldens:

npm run test:diff:golden

To run local unit tests:

npm run test:local

To run a subset of local unit tests, modify your local index.html, or start the dev server and navigate to the desired test page.

To run linting, visual-diff, and unit tests:

npm test

Versioning, Releasing & Deploying

All version changes should obey semantic versioning rules.

Commits and pull request merges to master will use frau-ci to automatically increment the package.json version and create a tag, which will subsequently trigger a deployment to NPM.

By default, the minor version will be bumped. To increment the major or patch version instead, use [increment major] or [increment patch] in your merge message.