NoRedInk/noredink-ui
1
1
Fork 0
mirror of https://github.com/NoRedInk/noredink-ui.git synced 2024-12-23 21:52:05 +03:00
Code Issues Packages Projects Releases Wiki Activity
3935313198
noredink-ui/styleguide-app/Examples/Icon.elm

189 lines
8.1 KiB
Elm
Raw Normal View History

Update the Icons in the styleguide
2018-06-22 20:39:00 +03:00
module Examples.Icon exposing (example)
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
{-|
@docs example, styles
-}
Update the Icons in the styleguide
2018-06-22 20:39:00 +03:00
import Assets exposing (Assets, assets)
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
import Css
Prep for 0.19 dual-publish (#163) * Use elm-css 16.0.0 * :skull: Ui.Checkbox V1 and V2 * s/Css.Foreign/Css.Global/g * :skull: Nri.Ui.Styles.V1 * :skull: BannerAlert.V1 * :skull: Modal.V1 * :skull: Dropdown.V1 * :skull: Select.V1 and V2 * :skull: Alert.V1 * :skull: Button.V1 and V2 * :skull: Divider.V1 * :skull: Icon.V1 and V2 * :skull: Outline.V1 * :skull: SegmentedControl.V1-V5 * :skull: TextArea.V1 and V2 * :skull: TextInput.V1 * delete the rest of the modules * actually more deletions * InputStyles v1 is unused * move to src-0.18 * do the 0.19 upgrade * select options are addressable by index * elm-css 16 * update scripts * elm-format * Update V2.elm * put the nbsp back * elm-format validation for both versions
2018-11-13 02:38:19 +03:00
import Css.Global
Update the Icons in the styleguide
2018-06-22 20:39:00 +03:00
import Html.Styled as Html exposing (Html)
import Html.Styled.Attributes exposing (css, style, title)
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
import ModuleExample exposing (Category(..), ModuleExample)
import Nri.Ui.Colors.V1 exposing (..)
upgrade use of Nri.Ui.Heading.V1 in the style guide
2019-07-23 17:53:43 +03:00
import Nri.Ui.Heading.V2 as Heading
Update imports to use new version of Nri.Ui.Icon
2019-05-29 20:20:30 +03:00
import Nri.Ui.Icon.V5 as Icon
add Nri.Ui.Text.V4 without headings
2019-07-23 17:09:07 +03:00
import Nri.Ui.Text.V4 as Text
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
{-| -}
Styleguide uses latest Icon / SegmentedControl
2018-03-29 13:58:41 +03:00
example : ModuleExample msg
example =
filename -> name
2019-05-03 19:56:43 +03:00
{ name = "Nri.Ui.Icon.V4"
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
, category = Icons
, content =
Use Text module for nicer headings :
2018-06-22 20:41:31 +03:00
[ viewIconSection "Mastery Icons"
Update the Icons in the styleguide
2018-06-22 20:39:00 +03:00
[ { icon = Icon.gardening, background = Dark, alt = "Gardening" }
, { icon = Icon.highFive, background = Dark, alt = "HighFive" }
, { icon = Icon.okay, background = Dark, alt = "Okay" }
, { icon = Icon.thumbsUp, background = Dark, alt = "ThumbsUp" }
, { icon = Icon.masteryBadge, background = Light, alt = "Badge " }
]
, viewIconSection "Stars and Flags"
[ { icon = Icon.starred, background = Light, alt = "Starred" }
, { icon = Icon.notStarred, background = Light, alt = "NotStarred" }
, { icon = Icon.flag, background = Light, alt = "Flag" }
]
, viewIconSection "Assignment Types"
[ { icon = Icon.assignmentTypeDiagnostic, background = Light, alt = "Diagnostic" }
, { icon = Icon.assignmentTypePractice, background = Light, alt = "Practice" }
, { icon = Icon.assignmentTypeQuiz, background = Light, alt = "Quiz" }
Icon V4: use SvgIcon for assignment types
2018-10-26 19:45:30 +03:00
, { icon = Icon.assignmentTypeQuickWrite, background = Light, alt = "QuickWrite" }
Merge branch 'master' into ink__guided-draft-icon Move guided draft icon to Icon V4
2018-10-29 19:51:12 +03:00
, { icon = Icon.assignmentTypeGuidedDraft, background = Light, alt = "GuidedDraft" }
Icon V4: use SvgIcon for assignment types
2018-10-26 19:45:30 +03:00
, { icon = Icon.assignmentTypePeerReview, background = Light, alt = "PeerReview" }
, { icon = Icon.assignmentTypeSelfReview, background = Light, alt = "SelfReview" }
Update the Icons in the styleguide
2018-06-22 20:39:00 +03:00
, { icon = Icon.submitting, background = Light, alt = "Submitting" }
, { icon = Icon.rating, background = Light, alt = "Rating" }
, { icon = Icon.revising, background = Light, alt = "Revising" }
Rearrange icon examples
2018-10-16 00:22:58 +03:00
, { icon = Icon.assignmentTypeWritingCycle, background = Light, alt = "WritingCycle" }
Update the Icons in the styleguide
2018-06-22 20:39:00 +03:00
, { icon = Icon.writingAssignment, background = Light, alt = "WritingAssignment" }
]
Add student assignment actions sectoin
2018-06-22 21:24:06 +03:00
, viewIconSection "Student Assignment Actions"
[ { icon = Icon.assignmentStartButtonPrimary, background = Light, alt = "Start primary" }
, { icon = Icon.assignmentStartButtonSecondary, background = Light, alt = "Start secondary" }
]
, viewIconSection "Teacher Assignment Actions"
Update the Icons in the styleguide
2018-06-22 20:39:00 +03:00
[ { icon = Icon.unarchive, background = Light, alt = "Unarchive" }
, { icon = Icon.share, background = Light, alt = "Share" }
, { icon = Icon.seeMore, background = Light, alt = "See More" }
, { icon = Icon.preview, background = Light, alt = "Preview" }
, { icon = Icon.performance, background = Light, alt = "Performance" }
, { icon = Icon.openClose, background = Light, alt = "OpenClose" }
Remove/reorg the icons further
2019-05-03 18:53:10 +03:00
, { icon = Icon.download, background = Light, alt = "Download" }
Update the Icons in the styleguide
2018-06-22 20:39:00 +03:00
]
, viewIconSection "Edit"
[ { icon = Icon.edit, background = Light, alt = "Edit" }
, { icon = Icon.editWriting, background = Light, alt = "EditWriting" }
]
, viewIconSection "Humans"
[ { icon = Icon.class, background = Light, alt = "Class" }
, { icon = Icon.leaderboard, background = Light, alt = "Leaderboard" }
, { icon = Icon.personBlue, background = Light, alt = "PersonBlue" }
]
, viewIconSection "Social Media"
[ { icon = Icon.facebook, background = Light, alt = "Facebook" }
, { icon = Icon.twitter, background = Light, alt = "Twitter" }
, { icon = Icon.clever, background = Light, alt = "Clever" }
]
, viewIconSection "Arrows and Carets"
[ { icon = Icon.arrowDown, background = Light, alt = "ArrowDown" }
, { icon = Icon.sortArrow, background = Light, alt = "SortArrow" }
]
, viewIconSection "Checkmarks"
[ { icon = Icon.checkMarkSvg, background = Light, alt = "CheckMarkSvg" }
]
, viewIconSection "Xs"
[ { icon = Icon.xSvg, background = Light, alt = "XSvg" }
]
, viewIconSection "Bangs"
[ { icon = Icon.exclamation, background = Light, alt = "Exclamation" }
, { icon = Icon.attention, background = Dark, alt = "Attention" }
]
, viewIconSection "Bulbs and Tips"
[ { icon = Icon.bulb, background = Light, alt = "Bulb" }
, { icon = Icon.lightBulb, background = Light, alt = "LightBulb" }
Remove/reorg the icons further
2019-05-03 18:53:10 +03:00
, { icon = Icon.helpSvg, background = Light, alt = "Help" }
Update the Icons in the styleguide
2018-06-22 20:39:00 +03:00
]
, viewIconSection "Locks and keys"
[ { icon = Icon.key, background = Light, alt = "Key" }
, { icon = Icon.lock, background = Light, alt = "Lock" }
]
, viewIconSection "Time"
[ { icon = Icon.calendar, background = Light, alt = "Calendar" }
, { icon = Icon.clock, background = Light, alt = "Clock" }
]
, viewIconSection "Uncategorized (SVGs)"
[ { icon = Icon.activity, background = Light, alt = "Activity" }
, { icon = Icon.compassSvg, background = Light, alt = "CompassSvg" }
, { icon = Icon.document, background = Light, alt = "Document" }
, { icon = Icon.flipper, background = Light, alt = "Flipper" }
, { icon = Icon.footsteps, background = Light, alt = "Footsteps" }
, { icon = Icon.gear, background = Light, alt = "Gear" }
Add pen icon
2018-08-14 00:41:09 +03:00
, { icon = Icon.pen, background = Light, alt = "Pen" }
Update the Icons in the styleguide
2018-06-22 20:39:00 +03:00
, { icon = Icon.newspaper, background = Light, alt = "Newspaper" }
, { icon = Icon.sort, background = Light, alt = "Sort" }
, { icon = Icon.speedometer, background = Light, alt = "Speedometer" }
Adds skip to the styleguide
2019-06-04 01:28:24 +03:00
, { icon = Icon.skip, background = Light, alt = "Skip" }
Remove the small checkmark and keep the equality sign
2019-06-04 01:43:28 +03:00
, { icon = Icon.equalitySign, background = Light, alt = "EqualitySign" }
Fix missing logo
2019-06-04 02:35:12 +03:00
, { icon = Icon.logo, background = Light, alt = "Logo" }
Update the Icons in the styleguide
2018-06-22 20:39:00 +03:00
]
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
]
}
Update the Icons in the styleguide
2018-06-22 20:39:00 +03:00
viewIconSection :
String
-> List { alt : String, background : Background, icon : Assets -> Icon.IconType }
-> Html msg
viewIconSection headerText icons =
Html.section []
upgrade use of Nri.Ui.Heading.V1 in the style guide
2019-07-23 17:53:43 +03:00
[ Heading.h2 [] [ Html.text headerText ]
Update the Icons in the styleguide
2018-06-22 20:39:00 +03:00
, Html.div [ css [ Css.displayFlex, Css.flexWrap Css.wrap ] ]
(List.map viewIcon icons)
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
]
type Background
= Light
| Dark
Update the Icons in the styleguide
2018-06-22 20:39:00 +03:00
toColor : Background -> Css.Color
toColor background =
case background of
Dark ->
blue
Light ->
frost
viewIcon : { alt : String, background : Background, icon : Assets -> Icon.IconType } -> Html msg
Styleguide uses latest Icon / SegmentedControl
2018-03-29 13:58:41 +03:00
viewIcon { alt, background, icon } =
Update the Icons in the styleguide
2018-06-22 20:39:00 +03:00
Html.div
[ css
[ Css.margin (Css.px 10)
, Css.width (Css.px 160)
, Css.boxShadow4 (Css.px 10) (Css.px 5) (Css.px 5) navy
, Css.displayFlex
, Css.flexDirection Css.column
, Css.alignItems Css.center
, Css.justifyContent Css.flexStart
]
]
[ Html.div
[ css
[ Css.displayFlex
, Css.alignItems Css.center
, Css.justifyContent Css.center
, Css.backgroundColor (toColor background)
, Css.height (Css.px 80)
, Css.width (Css.px 80)
, Css.margin (Css.px 10)
Make the svgs with their fill color set up properly green this will make it easer to tell which icons on the page are set up right and svgish
2019-04-06 02:30:26 +03:00
, Css.color green
Prep for 0.19 dual-publish (#163) * Use elm-css 16.0.0 * :skull: Ui.Checkbox V1 and V2 * s/Css.Foreign/Css.Global/g * :skull: Nri.Ui.Styles.V1 * :skull: BannerAlert.V1 * :skull: Modal.V1 * :skull: Dropdown.V1 * :skull: Select.V1 and V2 * :skull: Alert.V1 * :skull: Button.V1 and V2 * :skull: Divider.V1 * :skull: Icon.V1 and V2 * :skull: Outline.V1 * :skull: SegmentedControl.V1-V5 * :skull: TextArea.V1 and V2 * :skull: TextInput.V1 * delete the rest of the modules * actually more deletions * InputStyles v1 is unused * move to src-0.18 * do the 0.19 upgrade * select options are addressable by index * elm-css 16 * update scripts * elm-format * Update V2.elm * put the nbsp back * elm-format validation for both versions
2018-11-13 02:38:19 +03:00
, Css.Global.descendants
[ Css.Global.img
Update the Icons in the styleguide
2018-06-22 20:39:00 +03:00
[ Css.maxWidth (Css.pct 100)
, Css.maxHeight (Css.pct 100)
]
]
]
, title alt
]
[ Icon.icon { alt = alt, icon = icon assets }
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
]
Use Text module for nicer headings :
2018-06-22 20:41:31 +03:00
, Text.mediumBody [ Html.text alt ]
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
]
Reference in New Issue Copy Permalink