Skip to content

✨ Curology's React-based component library

License

Notifications You must be signed in to change notification settings

curology/radiance-ui

This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Folders and files

NameName
Last commit message
Last commit date
Oct 23, 2020
Nov 17, 2020
Oct 29, 2018
Nov 9, 2020
Nov 20, 2020
Nov 20, 2020
Nov 19, 2020
Oct 28, 2020
Nov 20, 2020
Nov 16, 2020
Nov 9, 2020
Nov 20, 2020
Sep 9, 2020
Nov 20, 2020
Nov 11, 2020
Oct 24, 2018
Oct 28, 2020
Nov 13, 2018
Nov 9, 2020
Nov 18, 2020
Nov 21, 2020
Nov 20, 2020
Oct 29, 2018
Nov 9, 2020
Nov 20, 2020

Repository files navigation

✨ Radiance UI

CircleCI

Curology's React based component library

Storybook

Radiance UI has a built in storybook. Every time a new commit is made to master, it is automatically deployed to https://radiance-ui.curology.com.

To run Storybook locally, use yarn run storybook.

Contributing

To contribute to Radiance UI, please create a PR with the following in the appropriate places:

  • Source code for the component
  • Tests
  • A storybook story

Tests

Tests can be run with yarn run test. Radiance uses Jest + Enzyme.

Local Development Setup

If you want to test out your changes with another repo that uses Radiance, we recommend using the link feature with npm or yarn.

Documentation

Documentation around usage, you can also see it with knobs at: https://radiance-ui.curology.com

Publishing to NPM

You'll need access to publish to NPM so this part only applies to a few people (mostly within the Curology organization). Once approved, merge your PR(s) into master and follow these steps:

  1. Run yarn build and commit the .size-snapshot.json change either as part of your PR or as part of the CHANGELOG.md change below
  2. Pull latest master and check out the master branch.
  3. Commit an update to the CHANGELOG.md file with details.
  4. Run yarn run publish-package to build the bundled files and publish to NPM.
  5. Push changes made to package.json to remote repository
  6. On GitHub, tag a release with the proper version and details. You can do that here.

Thanks

Chromatic

Thanks to Chromatic for providing the visual testing platform that helps us review UI changes and catch visual regressions!