Giter Club home page Giter Club logo

localize-components's People

Contributors

codacy-badger avatar dependabot[bot] avatar greenkeeper[bot] avatar imgbotapp avatar renovate-bot avatar renovate[bot] avatar seolhun avatar snyk-bot avatar

Stargazers

 avatar  avatar

Watchers

 avatar  avatar

localize-components's Issues

[components] change size function from padding to height, width

Purpose

  • change size function from padding to height, width

Why

  • Some components need align text. but, if hight padding styles, it is so difficult to align.

TODO List

  • define size padding to height, width
  • change size function

Additional context

  • I consider font size based on size props.

[Component] Add Sidebar, Header, Footer Components

Purpose

Build Header, Footer, Sidebar Components

What packages is changed?

  • @seolhun/localize-components-docs

  • @seolhun/localize-components-examples

  • @seolhun/localize-components

  • @seolhun/localize-components-atomic

  • @seolhun/localize-components-button

  • @seolhun/localize-components-modal

  • @seolhun/localize-components-form

  • @seolhun/localize-components-sidebar

  • @seolhun/localize-components-types

  • @seolhun/localize-components-styled-types

  • @seolhun/localize-components-styled-utils

  • @seolhun/localize-components-utils-event

[Docs] Core and Localize Components make the examples to show

What kind of change does this PR introduce?

  • localize-components
  • localize-components-atomic

Purpose

  • Show component playground and docs
  • Change stylesheet to js-inline-style(emotion)

Why

  • How to work localized component for others.
  • dynamic props for style using js

An in-range update of eslint-plugin-prettier is breaking the build 🚨


☝️ Important announcement: Greenkeeper will be saying goodbye πŸ‘‹ and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io


The devDependency eslint-plugin-prettier was updated from 3.1.2 to 3.1.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-prettier is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of eslint-config-prettier is breaking the build 🚨

The devDependency eslint-config-prettier was updated from 6.9.0 to 6.10.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-config-prettier is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

Commits

The new version differs by 4 commits.

  • 95a476e eslint-config-prettier v6.10.0
  • b7e3e90 Update npm packages
  • 04c79bf Disable @typescript-eslint/comma-spacing (#135)
  • d89bb10 Bump eslint from 6.6.0 to 6.8.0 (#136)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

[component] add component list to develop and process

Purpose

To develop localize-components and upgrade process.

Why

I see a lot of sites, and I'm trying to make good references.

Over time, more development needs have increased and complexity has increased.

We have determined that we need to improve these complex problems. We plan to create a list of UIs required for each version and update test codes and documents together.

Process

  1. Write README for Docs webstie
  2. Write a code
  3. Write a Test
  4. Write Storybook
  5. PR

Version

  • 1.0.0

Content Table

Atmoic

  • Button
  • ButtonGroup
  • Box
  • Card
  • Chip -> Tag
  • Typography
  • Image
  • Audio
  • Hr
  • Skeleton
  • Spinner
  • Progressbar
  • Collapse

Layout

  • Header
  • Sidebar
  • Footer
  • Menu

Forms

  • FormGroup
  • FormItem
  • FormLabel
  • FormHelp
  • Input
  • FileInput
  • Radio
  • Radio Group
  • Checkbox
  • Checkbox Group
  • Range
  • Switch
  • Select

Components

  • Breadcrumbs
  • Modal
  • Alert
  • Confirm
  • Dropdown
  • DropdownSearch
  • Drawer
  • Steps
  • Tabs
  • Tree
  • Popover
  • Toast
  • Tooltip

Icon

  • Icon
  • IconText

Grid

  • Container
  • Row
  • Col

Table (WIP)

DateTime (WIP)

Timezone (WIP)

Currencies (WIP)

An in-range update of eslint-plugin-import is breaking the build 🚨

The devDependency eslint-plugin-import was updated from 2.20.0 to 2.20.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-import is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

Commits

The new version differs by 23 commits.

  • 45f0860 Bump to v2.20.1
  • 5d00854 [Fix] order: Fix alphabetize for mixed requires and imports
  • bbd166b [Fix] export: Handle function overloading in *.d.ts
  • 4665ec5 [Fix] no-absolute-path: fix a crash with invalid import syntax
  • 392c6b9 [Fix] named: for importing from a module which re-exports named exports from a node_modules module
  • cc5bde5 [Tests] named: add failing test for #1446
  • aff3a46 [meta] fix "files" field to include/exclude the proper files
  • 986ba74 docs: fix a few spelling mistakes
  • 6274d96 [Tests] set eslint-plugin/consistent-output lint rule to always require test case output assertions
  • a4d301b [meta] add missing changelog links
  • 2d42464 [Tests] only run the linter once, not on every build
  • 26f232b [Tests] add eslint-plugin-eslint-plugin internally and fix violations
  • 99647f1 [Docs]: Update Tidelift language to enterprise
  • f84d457 no-duplicates: allow duplicate if one is namespace and other not
  • 7e71b50 [Fix] extensions: Fix scope regex

There are 23 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Add surge token to deploy example and docs

Purpose

  • Add surge auth token to deploy example and docs

Why

  • Change CI/CD from CircleCI to travis

TODO List

  • Add surge token in travis Env

Describe alternatives you've considered

  • None

Additional context

  • None

[Component] Fix Modal Component removing deprecated pakcage

Purpose

To enhanced Modal

Why

Modal dom has error

TODO List

  1. Removed deprecated package
  2. Add Theme
  3. Change Background DOM and zIndex

What packages is changed?

Contents

  • docs
  • examples

Components

  • localize-components
  • localize-components-atomic

Atomic Components

  • localize-components-button
  • localize-components-chip
  • localize-components-drawer
  • localize-components-form
  • localize-components-icons
  • localize-components-modal
  • localize-components-table

Types

  • localize-components-types
  • localize-components-types-style

Utils

  • localize-components-utils-event
  • localize-components-utils-style

[Component] Add figure components

Purpose

Add Figure components

Why

We need container with localize-styled figure

TODO List

  1. Circle
  2. ...

What packages is changed?

  • @seolhun/localize-components-docs

  • @seolhun/localize-components-examples

  • @seolhun/localize-components

  • @seolhun/localize-components-atomic

  • @seolhun/localize-components-button

  • @seolhun/localize-components-modal

  • @seolhun/localize-components-form

  • @seolhun/localize-components-types

  • @seolhun/localize-components-styled-types

  • @seolhun/localize-components-styled-utils

  • @seolhun/localize-components-utils-event

[Component] Migration style using emotion

Purpose

  • Change stylesheet to js-inline-style(emotion)

Why

  • Dynamic style using js
  • Component is based on js object or configuration

TODO List

  • Migration stylesheet to emotion
  • Update styled-types and styled-utils for emotion

An in-range update of eslint-config-prettier is breaking the build 🚨


☝️ Important announcement: Greenkeeper will be saying goodbye πŸ‘‹ and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io


The devDependency eslint-config-prettier was updated from 6.10.0 to 6.10.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-config-prettier is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

Commits

The new version differs by 13 commits.

  • a188a3c eslint-config-prettier v6.10.1
  • a5b25ac Fix Windows tests
  • 8126c58 Update readme
  • a91a6a5 Update versions in readme
  • 2a7fa6a Use proseWrap: never for better git diffs
  • b76e316 Recommend running the CLI helper tool using npx
  • 4366d25 Add empty .prettierrc to help editor extensions
  • 538dbb5 Use less of eslint-plugin-prettier
  • 7dffee0 Format markdown files with Prettier
  • 2a5b854 Update npm packages, including Prettier 2.0 changes
  • 855185f Remove TravisCI
  • 83705e8 Disable linebreak-style in test for Windows support
  • b6559bf Add GitHub Actions

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of @typescript-eslint/eslint-plugin is breaking the build 🚨

The devDependency @typescript-eslint/eslint-plugin was updated from 2.17.0 to 2.18.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@typescript-eslint/eslint-plugin is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

Release Notes for v2.18.0

2.18.0 (2020-01-27)

Bug Fixes

  • eslint-plugin: [explicit-module-boundary-types] false positive for returned fns (#1490) (5562ad5)
  • improve token types and add missing type guards (#1497) (ce41d7d)
  • eslint-plugin: [naming-convention] fix filter option (#1482) (718cd88)
  • eslint-plugin: fix property access on undefined error (#1507) (d89e8e8)
  • experimental-utils: widen type of settings property (#1527) (b515e47)
  • typescript-estree: error on unexpected jsdoc nodes (#1525) (c8dfac3)
  • typescript-estree: fix identifier tokens typed as Keyword (#1487) (77a1caa)

Features

  • eslint-plugin: add comma-spacing (#1495) (1fd86be)
  • eslint-plugin: add new rule prefer-as-const (#1431) (420db96)
  • eslint-plugin: create ban-ts-comment rule (#1361) (2a83d13)
  • eslint-plugin-internal: add prefer-ast-types-enum (#1508) (c3d0a3a)
  • experimental-utils: make RuleMetaData.docs optional (#1462) (cde97ac)
  • parser: improve scope-analysis types (#1481) (4a727fa)
Commits

The new version differs by 30 commits.

  • b835ec2 chore: publish v2.18.0
  • 367b18f docs(eslint-plugin): add script to generate the readme tables (#1524)
  • 03221d2 test: fix vscode launch configuration for windows (#1523)
  • f991764 chore(eslint-plugin): refactor explicit return type rules to share code (#1493)
  • c8dfac3 fix(typescript-estree): error on unexpected jsdoc nodes (#1525)
  • 6d1d2a2 test: fix coverage reports from codecov (#1528)
  • b515e47 fix(experimental-utils): widen type of settings property (#1527)
  • 67784d6 docs: extra 'a' in CONTRIBUTING.md (#1518)
  • afa7900 chore: enable prefer-ast-types-enum internal rule (#1514)
  • c3d0a3a feat(eslint-plugin-internal): add prefer-ast-types-enum (#1508)
  • 718cd88 fix(eslint-plugin): [naming-convention] fix filter option (#1482)
  • 802e347 chore(eslint-plugin): use getFixturesRootDir in tests (#1506)
  • 9ca65dc chore: update istanbul-reports to make tests quiet (#1509)
  • d89e8e8 fix(eslint-plugin): fix property access on undefined error (#1507)
  • 06731e7 test(eslint-plugin): cleanup no-use-before-define tests (#1505)

There are 30 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of @typescript-eslint/parser is breaking the build 🚨

The devDependency @typescript-eslint/parser was updated from 2.21.0 to 2.22.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@typescript-eslint/parser is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

Release Notes for v2.22.0

2.22.0 (2020-03-02)

Bug Fixes

  • eslint-plugin: [ban-types] add option extendDefaults (#1379) (ae7f7c5)
  • eslint-plugin: [default-param-last] handle param props (#1650) (3534c6e)
  • eslint-plugin: [no-implied-eval] correct logic for ts3.8 (#1652) (33e3e6f)

Features

  • eslint-plugin: [explicit-member-accessibility] autofix no-public (#1548) (dd233b5)
  • eslint-plugin: [typedef] add variable-declaration-ignore-function (#1578) (fc0a55e)
  • eslint-plugin: add new no-base-to-string rule (#1522) (8333d41)
  • eslint-plugin: add prefer-readonly-parameters (#1513) (3be9854)
  • eslint-plugin: additional annotation spacing rules for va… (#1496) (b097245)
Commits

The new version differs by 10 commits.

  • 5a097d3 chore: publish v2.22.0
  • 3be9854 feat(eslint-plugin): add prefer-readonly-parameters (#1513)
  • b097245 feat(eslint-plugin): additional annotation spacing rules for va… (#1496)
  • 33e3e6f fix(eslint-plugin): [no-implied-eval] correct logic for ts3.8 (#1652)
  • fc0a55e feat(eslint-plugin): [typedef] add variable-declaration-ignore-function (#1578)
  • 8333d41 feat(eslint-plugin): add new no-base-to-string rule (#1522)
  • dd233b5 feat(eslint-plugin): [explicit-member-accessibility] autofix no-public (#1548)
  • baf7c98 docs(eslint-plugin): [consistent-type-assertion] improve docs (#1651)
  • ae7f7c5 fix(eslint-plugin): [ban-types] add option extendDefaults (#1379)
  • 3534c6e fix(eslint-plugin): [default-param-last] handle param props (#1650)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Split grid component to Mono repo stand alones

Purpose

Change mono repo for Grid

Why

Grid is common and useful components

TODO List

  1. Split codes
    2 [ ] Add repo list docs and github

What packages is changed?

  • @seolhun/localize-components-docs
  • @seolhun/localize-components-examples
  • @seolhun/localize-components
  • @seolhun/localize-components-atomic
  • @seolhun/localize-components-button
  • @seolhun/localize-components-modal
  • @seolhun/localize-components-form
  • @seolhun/localize-components-types
  • @seolhun/localize-components-styled-types
  • @seolhun/localize-components-styled-utils
  • @seolhun/localize-components-utils-event

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

[Bundle] Migration TSC to Rollup with Webpack

Purpose

To exports external modules

Why

Module bundling with required library

TODO List

Wirte the rollup.config.js and install packages.

What packages is changed?

  • @seolhun/localize-components-docs

  • @seolhun/localize-components-examples

  • @seolhun/localize-components

  • @seolhun/localize-components-atomic

  • @seolhun/localize-components-button

  • @seolhun/localize-components-modal

  • @seolhun/localize-components-form

  • @seolhun/localize-components-types

  • @seolhun/localize-components-styled-types

  • @seolhun/localize-components-styled-utils

  • @seolhun/localize-components-utils-event

[Component] Add animation constats into styled-utils or types

Purpose

Animation constants to use commonly.

Why

All Components required animation.

What packages is changed?

  • docs
  • examples
  • localize-components
  • localize-components-atomic
  • localize-components-button
  • localize-components-chip
  • localize-components-drawer
  • localize-components-form
  • localize-components-icons
  • localize-components-modal
  • localize-components-styled-types
  • localize-components-styled-utils
  • localize-components-table
  • localize-components-types
  • localize-components-utils
  • localize-components-utils-event

[Component] Add GroupButtons components with radius

Purpose

Add Group buttons to bind buttons

Why

Buttons Group with radius

TODO List

  1. Add ButtonGroup.tsx
  2. Change radius style by props

What packages is changed?

  • @seolhun/localize-components-docs

  • @seolhun/localize-components-examples

  • @seolhun/localize-components

  • @seolhun/localize-components-atomic

  • @seolhun/localize-components-button

  • @seolhun/localize-components-modal

  • @seolhun/localize-components-form

  • @seolhun/localize-components-types

  • @seolhun/localize-components-styled-types

  • @seolhun/localize-components-styled-utils

  • @seolhun/localize-components-utils-event

Zapier Integration Test

Purpose

  • Write the purpose this task.

Why

  • Write the resonable backgrounds about this task.

TODO List

  • Write a next TODO list you think. if you think that task is done, let it empty.

Describe alternatives you've considered

  • A clear and concise description of any alternative solutions or features you've considered.

Additional context

  • Add any other context or screenshots about the feature request here.

What packages is changed?

Documents

  • @seolhun/localize-components-docs
  • @seolhun/localize-components-examples

Components

  • @seolhun/localize-components
  • @seolhun/localize-components-atomic

Mono Components

  • @seolhun/localize-components-button
  • @seolhun/localize-components-form
  • @seolhun/localize-components-grid
  • @seolhun/localize-components-icons
  • @seolhun/localize-components-modal
  • @seolhun/localize-components-sidebar

Utils

  • @seolhun/localize-components-hooks
  • @seolhun/localize-components-styled-utils
  • @seolhun/localize-components-utils-event

Types

  • @seolhun/localize-components-styled-types
  • @seolhun/localize-components-types

[Styled-Utils] Build Themes Props based on condition

Purpose

  1. for dynamic design based on props.
  2. for catch error checking color props validation.

Why

Localize component is built by props mainColor and subColor from developer or someone.

TODO List

  • Build Color Utils
    • check has ours themes
      • Themes[mainColor] ? Themes[mainColor] : mainColor
    • darken, lighten, based on (color, dim)
    • reverse option
      • (color, isReverse) or callback
      • ex) lighten background required darken color.

An in-range update of lerna is breaking the build 🚨


🚨 Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! πŸ’œ πŸššπŸ’¨ πŸ’š

Find out how to migrate to Snyk at greenkeeper.io


The devDependency lerna was updated from 3.20.2 to 3.21.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

lerna is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

Release Notes for v3.21.0

3.21.0 (2020-05-13)

Bug Fixes

  • publish: Canary releases without previous tags should not explode (c9eb590)

Features

  • project: Add getPackagesSync() export (068bdd7)
  • version: Ignore private packages completely with --no-private (a9b9f97)
Commits

The new version differs by 16 commits.

  • 3367257 chore(release): v3.21.0
  • a49d674 chore: npm audit did something? ugh minimist
  • 28e9941 chore: resolve kind-of 'vulnerability'
  • f280286 chore: resolve acorn 'vulnerability'
  • 068bdd7 feat(project): Add getPackagesSync() export
  • 1713635 refactor(project): Inline array flattener
  • e74a080 refactor(project): Don't mutate packageConfigs parameter
  • 6e3c864 refactor(project): Extract glob option logic into helper
  • f4e1a78 refactor(project): Internal default export -> named
  • 164cfaa refactor(version): Use Package#set() method to assign package version
  • 8dc2911 refactor(version): Avoid destructuring during graph node iteration
  • a9b9f97 feat(version): Ignore private packages completely with --no-private
  • 4691b93 refactor(publish): Avoid destructuring during graph node iteration
  • ee2fd0e refactor(publish): Eagerly filter private packages to avoid redundant operations
  • 7d36129 refactor(publish): DRY makeVersion() fallback

There are 16 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Change theme properties all

Purpose

  1. Change theme from origin to newer.
// Origin Theme
export interface ILocalizeTheme {
  primaryColor: LocalizeThemesType;
  secondaryColor: LocalizeThemesType;
  clickableColor: LocalizeThemesType;
  background: LocalizeThemesType;
  border: {
    color: LocalizeThemesType;
    radius: string;
    shadow: string;
  };
  grid: {
    containerGutter: {
      right: string;
      left: string;
    };
    rowGutter: {
      top: string;
      right: string;
      left: string;
    };
    columnGutter: {
      top: string;
      right: string;
      left: string;
      bottom: string;
    };
  };
  fonts: {
    color: {
      highlightColor: LocalizeThemesType;
      primaryColor: LocalizeThemesType;
      secondaryColor: LocalizeThemesType;
    };
    size: {
      h1: string;
      h2: string;
      h3: string;
      h4: string;
      h5: string;
      h6: string;
      p: string;
      big: string;
      medium: string;
      small: string;
    };
  };
}

// Newer Theme

export interface LocalizeThemeProps {
  type: string; // 'light' | 'dark';
  colors: {
    primary01: string;
    primary02: string;
    primary03: string;
    primaryBackground01: string;
    primaryBackground02: string;
    primaryBackground03: string;
    uiColor01: string;
    uiColor02: string;
    uiColor03: string;
    uiColor04: string;
    uiColor05: string;
    uiColor06: string;
    uiColor07: string;
    uiColor08: string;
    uiColor09: string;
    uiColor010: string;
    error: string;
    warning: string;
  };
  fonts: LocalizeThemeFontsProps;
  layout: {
    backgroundColor: string;
    fontColor: string;
  };
}

Why

The Localize component original concept is that theme is changed by props. This will be valid concept after next version release also.
But, I have a mistake about theme missing scalability. Current theme values is not good to read and develop for all components.
So I will change all themes properties like newer theme comments, and will be released as version 0.6.0.

TODO List

  1. Declare theme for newer
  2. Change style-utils and then all components. and then remove all mainColor, subColor props.
  3. Remove old theme and style types.
  4. Fix docs and examples removing main, subColor props.
  5. Write theme description for development in docs

Describe alternatives you've considered

I decide to remove main, sub Color props. This decision was so difficult . but, The React context already existed by emotion js for theme. so, Theme changed by others props like mainColor is like side-effect.

Additional context

Will be Removed mainColor and subColor like color props in all components.


What packages is changed?

Documents

  • @seolhun/localize-components-docs
  • @seolhun/localize-components-examples

Components

  • @seolhun/localize-components
  • @seolhun/localize-components-atomic
  • @seolhun/localize-components-icons

Mono Components

  • @seolhun/localize-components-form
  • @seolhun/localize-components-grid
  • @seolhun/localize-components-sidebar

Utils

  • @seolhun/localize-components-hooks
  • @seolhun/localize-components-styled-utils
  • @seolhun/localize-components-utils-event

Types

  • @seolhun/localize-components-styled-types
  • @seolhun/localize-components-types

Add prepare scripts for github development mode

Purpose

  • for UnPublished version

Why

  • Develop version for usage

TODO List

  • Add npm prepare script

Describe alternatives you've considered

  • None

Additional context

  • None

What packages is changed?

Documents

  • @seolhun/localize-components-docs
  • @seolhun/localize-components-examples

Components

  • @seolhun/localize-components
  • @seolhun/localize-components-atomic

Mono Components

  • @seolhun/localize-components-button
  • @seolhun/localize-components-form
  • @seolhun/localize-components-modal
  • @seolhun/localize-components-sidebar

Utils

  • @seolhun/localize-components-hooks
  • @seolhun/localize-components-styled-utils
  • @seolhun/localize-components-utils-event

Types

  • @seolhun/localize-components-styled-types
  • @seolhun/localize-components-types

An in-range update of @typescript-eslint/eslint-plugin is breaking the build 🚨


☝️ Important announcement: Greenkeeper will be saying goodbye πŸ‘‹ and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io


The devDependency @typescript-eslint/eslint-plugin was updated from 2.24.0 to 2.25.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@typescript-eslint/eslint-plugin is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

Release Notes for v2.25.0

2.25.0 (2020-03-23)

Bug Fixes

Features

  • eslint-plugin: [no-unnec-type-assertion] allow const assertions (#1741) (f76a1b3)
  • eslint-plugin: [no-unnecessary-condition] ignore basic array indexing false positives (#1534) (2b9603d)
  • eslint-plugin: add class-literal-property-style rule (#1582) (b2dbd89)
  • experimental-utils: expose ast utility functions (#1670) (3eb5d45)
Commits

The new version differs by 19 commits.

  • 9cd3e4f chore: publish v2.25.0
  • b2dbd89 feat(eslint-plugin): add class-literal-property-style rule (#1582)
  • 3eb5d45 feat(experimental-utils): expose ast utility functions (#1670)
  • 2b9603d feat(eslint-plugin): [no-unnecessary-condition] ignore basic array indexing false positives (#1534)
  • c82d121 chore(typescript-estree): remove unfinished comment (#1770)
  • 199863d fix(eslint-plugin): [quotes] false positive with backtick in import equals statement (#1769)
  • 6646959 fix(eslint-plugin): fix message of no-base-to-string (#1755)
  • f76a1b3 feat(eslint-plugin): [no-unnec-type-assertion] allow const assertions (#1741)
  • 09d8afc fix(typescript-estree): export * regression from 133f622f (#1751)
  • 52b061e chore: try fetching all tags and history in canary job
  • 19cc9a9 chore: try fetching all tags and history in canary job
  • 61a779c chore: try fetching all history in canary job
  • d6e273d chore: standardise issue templates (#1760)
  • abf1a2f fix(eslint-plugin-tslint): fix tslintConfig memoization key (#1719)
  • 3814d4e fix: only run publish_canary_version on master

There are 19 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of @typescript-eslint/parser is breaking the build 🚨

The devDependency @typescript-eslint/parser was updated from 2.17.0 to 2.18.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@typescript-eslint/parser is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

Release Notes for v2.18.0

2.18.0 (2020-01-27)

Bug Fixes

  • eslint-plugin: [explicit-module-boundary-types] false positive for returned fns (#1490) (5562ad5)
  • improve token types and add missing type guards (#1497) (ce41d7d)
  • eslint-plugin: [naming-convention] fix filter option (#1482) (718cd88)
  • eslint-plugin: fix property access on undefined error (#1507) (d89e8e8)
  • experimental-utils: widen type of settings property (#1527) (b515e47)
  • typescript-estree: error on unexpected jsdoc nodes (#1525) (c8dfac3)
  • typescript-estree: fix identifier tokens typed as Keyword (#1487) (77a1caa)

Features

  • eslint-plugin: add comma-spacing (#1495) (1fd86be)
  • eslint-plugin: add new rule prefer-as-const (#1431) (420db96)
  • eslint-plugin: create ban-ts-comment rule (#1361) (2a83d13)
  • eslint-plugin-internal: add prefer-ast-types-enum (#1508) (c3d0a3a)
  • experimental-utils: make RuleMetaData.docs optional (#1462) (cde97ac)
  • parser: improve scope-analysis types (#1481) (4a727fa)
Commits

The new version differs by 30 commits.

  • b835ec2 chore: publish v2.18.0
  • 367b18f docs(eslint-plugin): add script to generate the readme tables (#1524)
  • 03221d2 test: fix vscode launch configuration for windows (#1523)
  • f991764 chore(eslint-plugin): refactor explicit return type rules to share code (#1493)
  • c8dfac3 fix(typescript-estree): error on unexpected jsdoc nodes (#1525)
  • 6d1d2a2 test: fix coverage reports from codecov (#1528)
  • b515e47 fix(experimental-utils): widen type of settings property (#1527)
  • 67784d6 docs: extra 'a' in CONTRIBUTING.md (#1518)
  • afa7900 chore: enable prefer-ast-types-enum internal rule (#1514)
  • c3d0a3a feat(eslint-plugin-internal): add prefer-ast-types-enum (#1508)
  • 718cd88 fix(eslint-plugin): [naming-convention] fix filter option (#1482)
  • 802e347 chore(eslint-plugin): use getFixturesRootDir in tests (#1506)
  • 9ca65dc chore: update istanbul-reports to make tests quiet (#1509)
  • d89e8e8 fix(eslint-plugin): fix property access on undefined error (#1507)
  • 06731e7 test(eslint-plugin): cleanup no-use-before-define tests (#1505)

There are 30 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.