HTML custom element for the use of drawing attention to additional interface information.
There are two important parts of every Auro component. The class and the custom element. The class is exported and then used as part of defining the Web Component. When importing this component as described in the install section, the class is imported and the auro-badge custom element is defined automatically.
To protect from versioning conflicts with other instances of the component being loaded, it is recommended to use our registerComponent(name) method and pass in a unique name.
import './node_modules/@aurodesignsystem/auro-badge';
registerComponent('custom-badge');This will create a new custom element that you can use in your HTML that will function identically to the auro-badge element.
For the most up to date information on UI development browser support
$ npm i @aurodesignsystem/auro-badgeInstalling as a direct, dev or peer dependency is up to the user installing the package. If you are unsure as to what type of dependency you should use, consider reading this stack overflow answer.
The use of any Auro custom element has a dependency on the Auro Design Tokens.
Defining the component dependency within each component that is using the <auro-badge> component.
import "@aurodesignsystem/auro-badge";Reference component in HTML
<auro-badge>Nonstop</auro-badge>In cases where the project is not able to process JS assets, there are pre-processed assets available for use. See -- auro-badge__bundled.js for modern browsers. Legacy browsers such as IE11 are no longer supported.
WARNING! When installing into your application environment, DO NOT use @latest for the requested version. Risks include unknown MAJOR version releases and instant adoption of any new features and possible bugs without developer knowledge. The @latest wildcard should NEVER be used for production customer-facing applications. You have been warned.
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@aurodesignsystem/design-tokens@4.9.2/dist/tokens/CSSCustomProperties.css" />
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@aurodesignsystem/webcorestylesheets@5.1.2/dist/bundled/essentials.css" />
<script src="https://cdn.jsdelivr.net/npm/@aurodesignsystem/auro-badge@3.3.1/dist/auro-badge__bundled.js" type="module"></script>The auro-badge use cases include:
- Additional information to draw attention to a specific area of the interface
- Advising the user of a specific action or status
<auro-badge>Nonstop</auro-badge>In order to develop against this project, if you are not part of the core team, you will be required to fork the project prior to submitting a pull request.
Please be sure to review the contribution guidelines for this project. Please make sure to pay special attention to the conventional commits section of the document.
Once the project has been cloned to your local resource and you have installed all the dependencies you will need to open a shell session to run the dev server.
$ npm run devOpen localhost:8000
If running separate sessions is preferred, please run the following commands in individual terminal shells.
$ npm run build:watch
$ npm run serveThe custom element API file is generated in the build and committed back to the repo with a version change. If the API doc has changed without a version change, author's are to run npm run build:api to generate the doc and commit to version control.
Automated tests are required for every Auro component. See .\test\auro-badge.test.js for the tests for this component. Run npm test to run the tests and check code coverage. Tests must pass and meet a certain coverage threshold to commit. See the testing documentation for more details.
Bundled assets are only generated in the remote and not merged back to this repo. To review and/or test a bundled asset locally, run $ npm run bundler to generate assets.