|elm-version||0.18.0 <= v < 0.19.0|
|Committed At||2018-05-11 10:35:39 UTC|
|elm-lang/svg||2.0.0 <= v < 3.0.0||2.0.0|
|wernerdegroot/listzipper||3.0.0 <= v < 4.0.0||3.1.1|
|tesk9/accessible-html||3.0.0 <= v < 4.0.0||3.1.0|
|rtfeldman/elm-css-util||1.0.2 <= v < 2.0.0||1.0.2|
|rtfeldman/elm-css-helpers||2.1.0 <= v < 3.0.0||2.1.0|
|rtfeldman/elm-css||11.2.0 <= v < 12.0.0||11.2.0|
|pablohirafuji/elm-markdown||2.0.4 <= v < 3.0.0||2.0.5|
|elm-lang/html||2.0.0 <= v < 3.0.0||2.0.0|
|elm-lang/core||5.1.1 <= v < 6.0.0||5.1.1|
|NoRedInk/view-extra||2.0.0 <= v < 3.0.0||2.0.0|
|NoRedInk/nri-elm-css||5.0.0 <= v <= 5.0.0||5.0.0|
UI widgets we use.
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
We should change this process if we feel it's not working for us!
This repo contains an app showcasing all of these UI widgets.
To see them locally:
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.
Run tests with
Travis will run
make ci to verify everything looks good.
You can run this locally to catch errors before you push!