Terra Core

• Packages
  • Versioning
  • Status
  • Deprecated
• Supported Browsers
• Internationalization (I18n)
  • Packages Requiring I18n
• Contributing
• Local Development
• Local Development using Docker (Dev Containers)
• LICENSE

Packages

Versioning

When a component reaches v1.0.0., it is considered to be stable and will follow SemVer for versioning.

1. MAJOR versions represent breaking changes
2. MINOR versions represent added functionality in a backwards-compatible manner
3. PATCH versions represent backwards-compatible bug fixes

Consult the component CHANGELOGs, related issues, and PRs for more information.

We view the React.js props API of our components as our main public API. We use this to guide us when versioning components.

Prior to components reaching v1.0.0, a component is considered to be in a beta stage. Components in beta stage may include breaking changes, new features, and bug fixes all within v0.x.x releases.

Status

Terra Package	Version	Status	Dependencies
terra-action-footer
terra-action-header
terra-alert
terra-arrange
terra-avatar
terra-badge
terra-base
terra-breakpoints
terra-button
terra-button-group
terra-card
terra-content-container
terra-demographics-banner
terra-dialog
terra-divider
terra-dropdown-button
terra-dynamic-grid
terra-form-checkbox
terra-form-field
terra-form-fieldset
terra-form-input
terra-form-radio
terra-form-select
terra-form-textarea
terra-grid
terra-heading
terra-hyperlink
terra-i18n
terra-icon
terra-image
terra-list
terra-mixins
terra-overlay
terra-paginator
terra-profile-image
terra-progress-bar
terra-responsive-element
terra-scroll
terra-search-field
terra-section-header
terra-show-hide
terra-signature
terra-spacer
terra-status
terra-status-view
terra-table
terra-tag
terra-text
terra-toggle
terra-toggle-button
terra-toggle-section-header
terra-visually-hidden-text

Deprecated

Terra Package	Version	Status	Dependencies
terra-form
terra-i18n-plugin
terra-legacy-theme
terra-modal

Supported Browsers

Browser	Version
Chrome & Chrome for Android	Current
Edge	Current
Firefox	Current
Internet Explorer	10 & 11
Safari & Mobile Safari	Current

Internationalization (I18n)

Please review Terra's Internationalization documentation for more information. Included are directions on consumption and how internationalization is setup.

Packages Requiring I18n

• terra-action-header
• terra-alert
• terra-demographics-banner
• terra-dialog
• terra-form-checkbox
• terra-form-field
• terra-form-radio
• terra-form-select
• terra-i18n
• terra-overlay
• terra-search-field
• terra-show-hide
• terra-status-view

Contributing

Please read through our contributing guidelines. Included are directions for issue reporting and pull requests.

Local Development

1. Install Node Version Manager (NVM) and Node. The root directory contains a .nvmrc file that specifies terra-core's node version. Once NVM is installed and you are within the root directory, your version of node will change to this version.
2. Install docker https://www.docker.com/ to run browser tests.
3. Install dependencies and run tests.

npm install
npm run test

Local Development using Docker (Dev Containers)

1. Install Docker.
2. Install Microsoft VS Code
3. Clone this repo.
4. Open this repo in VS Code.
5. Install the Dev Container extension.
   • Navigate to View -> Extension -> Search for and install Dev Containers (or "ms-vscode-remote.remote-containers")
   • More information on Dev Containers
6. Build the dev container.
   • Make sure you are connected to the Cerner VPN when building this container the first time.
   • Navigate to View -> Command Palette -> Open Workspace In Container or Reopen In Container.
7. You're now running in a dev container. Use the terminal of the dev container to issue any npm commands.
8. Before running any WDIO tests, make sure to perform the following steps:
   • Open a new terminal (outside the dev container) and navigate to ".devcontainer/" path in your repository.
   • Execute the command "docker compose -f docker-compose-wdio.yml up". Selenium hub should spin up. Leave this running in the background. If you see errors saying "container name already exists", run "docker container prune" command followed by pressing "y" to clear up any unused containers and try running the previous command again.
   • You can now run npm run test:docker or npm run wdio:docker commands to run WDIO tests from inside the Dev Container.
   • NOTE: Optionally, if you want to run other WDIO commands in the dev container, you can also edit the root package.json file WDIO scripts to include --disableSeleniumService=true flag. This will disable the selenium service from spinning up again. For example:

     "scripts": {
      "wdio-lowlight": "terra wdio --disableSeleniumService=true --themes clinical-lowlight-theme"
      }

LICENSE

Copyright 2017 - 2019 Cerner Innovation, Inc.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.