noredink-ui/elm-package.json

70 lines
2.2 KiB
JSON
Raw Normal View History

2017-11-15 04:47:42 +03:00
{
2018-06-27 20:16:09 +03:00
"version": "5.6.0",
2018-02-12 23:12:09 +03:00
"summary": "UI Widgets we use at NRI",
"repository": "https://github.com/NoRedInk/noredink-ui.git",
"license": "BSD3",
"source-directories": [
"src"
],
"exposed-modules": [
"Nri.Ui.Alert.V1",
2018-03-01 01:01:42 +03:00
"Nri.Ui.AssetPath",
2018-02-12 23:12:09 +03:00
"Nri.Ui.BannerAlert.V1",
"Nri.Ui.Button.V1",
"Nri.Ui.Button.V2",
2018-02-12 23:12:09 +03:00
"Nri.Ui.Checkbox.V1",
2018-03-20 01:53:58 +03:00
"Nri.Ui.Checkbox.V2",
2018-06-15 04:14:47 +03:00
"Nri.Ui.Checkbox.V3",
2018-06-27 22:15:23 +03:00
"Nri.Ui.Colors.Extra",
"Nri.Ui.Colors.V1",
2018-02-12 23:12:09 +03:00
"Nri.Ui.Divider.V1",
2018-04-16 23:13:31 +03:00
"Nri.Ui.Dropdown.V1",
2018-02-12 23:12:09 +03:00
"Nri.Ui.Effects.V1",
2018-03-17 03:31:04 +03:00
"Nri.Ui.Fonts.V1",
Extract `Nri.Icon` from the monolith The recommendation is to break the styles API rather than the view API when moving something out of the monolith into this repo. `Nri.Icon` is not really setup for that sort of breakage. If we would prefer to have the styles break rather than the view, that will take more work. Work that can be done independent of the extraction. The transition in the monolith ought to look something like: ```elm module Nri.Icon exposing (..) import Html exposing (Html) import Nri.SvgSprite import Nri.Ui.Icon.V1 exposing (Assets, IconType) icon : { alt : String, icon : IconType } -> Html msg icon config = Nri.Ui.Icon.V1.icon assets assets : Assets {} assets = { activity = Nri.SvgSprite.activity , arrowDown = Nri.SvgSprite.arrowDown , attention_svg = Nri.Assets.attention_svg ... } ``` So hopefully, the change is still very small on the monolith side. There's maybe a bigger concern than which API breaks. `Nri.Icon` has some behavior for a11y. We could definitely change the internals over during the extraction. But, since all of these changes are value-level changes, it's very likely that we'll break something in the process. That's a bigger concern because instead of affecting the handful of Engineers working at NRI, we would be affecting the millions of people using the site. We shouldn't fear making those kinds of changes. However, we should make them when we can give them the appropriate attention they deserve. Not when one person is trying to move as fast as possible to avoid race conditions of moving modules between repos.
2018-03-29 03:34:56 +03:00
"Nri.Ui.Icon.V1",
"Nri.Ui.Icon.V2",
2018-06-22 20:58:11 +03:00
"Nri.Ui.Icon.V3",
2018-05-31 03:22:17 +03:00
"Nri.Ui.InputStyles",
2018-02-12 23:12:09 +03:00
"Nri.Ui.Modal.V1",
"Nri.Ui.Outline.V1",
"Nri.Ui.Page.V1",
2018-02-12 23:12:09 +03:00
"Nri.Ui.Palette.V1",
2018-06-27 22:15:23 +03:00
"Nri.Ui.PremiumCheckbox.V1",
2018-03-24 05:05:34 +03:00
"Nri.Ui.SegmentedControl.V1",
2018-03-27 23:42:40 +03:00
"Nri.Ui.SegmentedControl.V2",
"Nri.Ui.SegmentedControl.V3",
"Nri.Ui.SegmentedControl.V4",
"Nri.Ui.SegmentedControl.V5",
2018-04-17 01:51:17 +03:00
"Nri.Ui.Select.V1",
2018-04-18 18:01:31 +03:00
"Nri.Ui.Select.V2",
2018-02-12 23:12:09 +03:00
"Nri.Ui.Styles.V1",
2018-04-24 19:45:53 +03:00
"Nri.Ui.Table.V1",
"Nri.Ui.Table.V2",
2018-02-12 23:12:09 +03:00
"Nri.Ui.Tabs.V1",
2018-03-02 00:34:44 +03:00
"Nri.Ui.Text.Writing.V1",
2018-02-12 23:12:09 +03:00
"Nri.Ui.Text.V1",
2018-05-17 13:19:51 +03:00
"Nri.Ui.Text.V2",
2018-02-12 23:12:09 +03:00
"Nri.Ui.TextArea.V1",
2018-05-18 11:18:04 +03:00
"Nri.Ui.TextArea.V2",
2018-06-01 01:07:15 +03:00
"Nri.Ui.TextArea.V3",
"Nri.Ui.TextInput.V1",
2018-05-25 23:35:11 +03:00
"Nri.Ui.TextInput.V2",
2018-06-01 01:07:15 +03:00
"Nri.Ui.TextInput.V3",
"Nri.Ui"
2018-02-12 23:12:09 +03:00
],
"dependencies": {
"NoRedInk/view-extra": "2.0.0 <= v < 3.0.0",
"elm-lang/core": "5.1.1 <= v < 6.0.0",
"elm-lang/html": "2.0.0 <= v < 3.0.0",
Extract `Nri.Icon` from the monolith The recommendation is to break the styles API rather than the view API when moving something out of the monolith into this repo. `Nri.Icon` is not really setup for that sort of breakage. If we would prefer to have the styles break rather than the view, that will take more work. Work that can be done independent of the extraction. The transition in the monolith ought to look something like: ```elm module Nri.Icon exposing (..) import Html exposing (Html) import Nri.SvgSprite import Nri.Ui.Icon.V1 exposing (Assets, IconType) icon : { alt : String, icon : IconType } -> Html msg icon config = Nri.Ui.Icon.V1.icon assets assets : Assets {} assets = { activity = Nri.SvgSprite.activity , arrowDown = Nri.SvgSprite.arrowDown , attention_svg = Nri.Assets.attention_svg ... } ``` So hopefully, the change is still very small on the monolith side. There's maybe a bigger concern than which API breaks. `Nri.Icon` has some behavior for a11y. We could definitely change the internals over during the extraction. But, since all of these changes are value-level changes, it's very likely that we'll break something in the process. That's a bigger concern because instead of affecting the handful of Engineers working at NRI, we would be affecting the millions of people using the site. We shouldn't fear making those kinds of changes. However, we should make them when we can give them the appropriate attention they deserve. Not when one person is trying to move as fast as possible to avoid race conditions of moving modules between repos.
2018-03-29 03:34:56 +03:00
"elm-lang/svg": "2.0.0 <= v < 3.0.0",
2018-02-12 23:12:09 +03:00
"pablohirafuji/elm-markdown": "2.0.4 <= v < 3.0.0",
2018-05-02 00:31:02 +03:00
"rtfeldman/elm-css": "13.1.1 <= v < 15.0.0",
2018-02-12 23:12:09 +03:00
"rtfeldman/elm-css-helpers": "2.1.0 <= v < 3.0.0",
"rtfeldman/elm-css-util": "1.0.2 <= v < 2.0.0",
"tesk9/accessible-html": "3.0.0 <= v < 4.0.0",
"tesk9/accessible-html-with-css": "1.0.1 <= v < 2.0.0",
2018-02-12 23:12:09 +03:00
"wernerdegroot/listzipper": "3.0.0 <= v < 4.0.0"
},
"elm-version": "0.18.0 <= v < 0.19.0"
2017-11-15 04:47:42 +03:00
}