Component Library package & Component Catalog app code
Go to file
2018-04-17 08:15:44 -07:00
src/Nri Merge branch 'master' into extract-select 2018-04-17 07:56:22 -07:00
styleguide-app Merge branch 'master' into extract-select 2018-04-17 07:56:22 -07:00
tests Add tests for checkbox 2018-03-27 15:59:09 +02:00
.gitignore Stop ignoring Icon modules 2018-03-29 09:57:20 +02:00
.travis.yml Merge branch 'master' into joneshf-patch-1 2018-03-28 19:56:09 +02:00
elm-package.json Bump version to 4.7.0 2018-04-17 08:15:44 -07:00
LICENSE Initial commit 2017-11-14 16:24:25 -08:00
Makefile disallow major changes in Travis 2018-03-30 09:10:39 -05:00
package-lock.json set versions with npm 2018-03-27 16:42:26 -05:00
package.json set versions with npm 2018-03-27 16:42:26 -05:00
README.md Add a section on our versioning policy 2018-03-30 16:54:02 +02:00

noredink-ui

UI widgets we use.

Versioning policy

We try to avoid breaking changes and the associated major version bumps in this package. The reason for that is to avoid the following scenario:

  |
  x   4.6.0: Adding RadioButton widget
  |
  x   5.0.0: Breaking change in the TextArea widget
  |
  x   5.0.1: Styling fix in the Checkbox widget
  |

Suppose you just released version 5.0.1, a small styling fix in the checkbox widget, for a story you're working on. If the project you're working in currently pulls in noredink-ui at version 4.x, then getting to your styling fix means pulling in a new major version of noredink-ui. This breaks all TextArea widgets across the project, so those will need to be fixed before you can do anything else, potentially a big effort.

To prevent these big Yaks from suddenly showing up in seemingly trivial tasks we prefer to avoid breaking changes in the package. Instead when we need to make a breaking change in a widget, we create a new module for it Nri.Ui.MyWidget.VX.

We should change this process if we feel it's not working for us!

Examples

This repo contains an app showcasing all of these UI widgets.

To see them locally:

make styleguide-app/elm.js

Open styleguide-app/index.html in your browser.

Alternatively, you may use elm-reactor. Please be aware that you'll need to globally install fonts (in particular, Muli) if you go this route.

Tests

Run tests with

make test

CI (Travis)

Travis will run make ci to verify everything looks good. You can run this locally to catch errors before you push!