Protei/PromucFlow_constructor
2
0
Fork 0
Code Issues Pull Requests Actions 3 Packages Projects Releases Wiki Activity
2e783f1f62
PromucFlow_constructor/app/client/packages/design-system/widgets/package.json

32 lines
879 B
JSON
Raw Normal View History

chore: Yarn workspaces + Storybook + WDS (#20776)
2023-03-03 06:47:35 +00:00
{
feat: wds button refactoring (#21849) ## Description 1. Moved `wds` to the `design-system` folder. 2. Added `headless` package and `HeadlessButton`. 3. Added `theming` package. `ThemeProvider` and two classes were created to work with tokens([TokensAccessor](https://github.com/appsmithorg/appsmith/pull/21849/files#diff-58832e8b8e8017648929473a90eb716e6a2671ba1749be3d4c5665b093bc3dc3)) and colors([ColorsAccessor](https://github.com/appsmithorg/appsmith/pull/21849/files#diff-f515e0eefc418c8bfc0710572e83a0029bd94f2fb975853f71730e5b11c774bd)) 5. The token structure has been changed. The same class(TokensAccessor) is now used to create CSS variables and tokens for Figma([themeTokens.json](https://github.com/appsmithorg/appsmith/pull/21849/files#diff-5ad75b848cb4254c0bd0bb0bf6a89eeccb628dc0012752172654e12e62d570d9)) The final storybook is [here](https://widget-design-system-b1p6g13iq-get-appsmith.vercel.app/?path=/story/design-system-widgets--button). ## Type of change - New feature (non-breaking change which adds functionality) - Chore (housekeeping or task changes that don't impact user perception) - This change requires a documentation update ## How Has This Been Tested? - Manual ## Checklist: ### Dev activity - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [x] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag --------- Co-authored-by: Valera Melnikov <melnikov.vv@greendatasoft.ru>
2023-04-05 12:39:11 +00:00
"name": "@design-system/widgets",
chore: Yarn workspaces + Storybook + WDS (#20776)
2023-03-03 06:47:35 +00:00
"version": "1.0.0",
"main": "src/index.ts",
"author": "Valera Melnikov <valera@appsmith.com>, Pawan Kumar <pawan@appsmith.com>",
"license": "MIT",
chore: improve husky and lint-staged checks (#21679) ## Description 1. Update husky, prettier and lint-staged then move them to devDependencies 2. Configure husky and lint-staged 3. Impriove rules for the lint commands 4. Fix errors of eslint and prettier. 5. Remove redundant files ## Type of change - Chore (housekeeping or task changes that don't impact user perception) Co-authored-by: Valera Melnikov <melnikov.vv@greendatasoft.ru>
2023-03-23 11:32:18 +00:00
"scripts": {
chore: move local dependency to packages (#23395) ## Description 1. Move everything related to client from app folder to client folder (`.yarn`, `yarn.lock`, package.json, .gitignore) 2. Move `ast` and `rst` to client packages 3. Fix running scripts in packages 4. Add running unit tests in packages in CI TODO: It is necessary to consider enabling the `nmHoistingLimits: workspaces` option, since now all packages are hoisted to the root, there may be issues with dependencies in workspaces. Also, there is a possibility of implicit use of packages. https://yarnpkg.com/configuration/yarnrc#nmHoistingLimits #### PR fixes following issue(s) Fixes #23333 #### Type of change - Chore (housekeeping or task changes that don't impact user perception) ## Testing #### How Has This Been Tested? - [x] Manual - [x] Jest - [x] Cypress ## Checklist: #### Dev activity - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag Co-authored-by: Valera Melnikov <melnikov.vv@greendatasoft.ru>
2023-05-22 12:55:46 +00:00
"lint": "yarn g:lint",
"prettier": "yarn g:prettier",
"test:unit": "yarn g:jest"
chore: improve husky and lint-staged checks (#21679) ## Description 1. Update husky, prettier and lint-staged then move them to devDependencies 2. Configure husky and lint-staged 3. Impriove rules for the lint commands 4. Fix errors of eslint and prettier. 5. Remove redundant files ## Type of change - Chore (housekeeping or task changes that don't impact user perception) Co-authored-by: Valera Melnikov <melnikov.vv@greendatasoft.ru>
2023-03-23 11:32:18 +00:00
},
chore: Yarn workspaces + Storybook + WDS (#20776)
2023-03-03 06:47:35 +00:00
"dependencies": {
chore: move local dependency to packages (#23395) ## Description 1. Move everything related to client from app folder to client folder (`.yarn`, `yarn.lock`, package.json, .gitignore) 2. Move `ast` and `rst` to client packages 3. Fix running scripts in packages 4. Add running unit tests in packages in CI TODO: It is necessary to consider enabling the `nmHoistingLimits: workspaces` option, since now all packages are hoisted to the root, there may be issues with dependencies in workspaces. Also, there is a possibility of implicit use of packages. https://yarnpkg.com/configuration/yarnrc#nmHoistingLimits #### PR fixes following issue(s) Fixes #23333 #### Type of change - Chore (housekeeping or task changes that don't impact user perception) ## Testing #### How Has This Been Tested? - [x] Manual - [x] Jest - [x] Cypress ## Checklist: #### Dev activity - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag Co-authored-by: Valera Melnikov <melnikov.vv@greendatasoft.ru>
2023-05-22 12:55:46 +00:00
"@design-system/headless": "workspace:^",
"@design-system/theming": "workspace:^",
chore: replace emotion/sheet to emotion/css (#27827) ## Description Replace emotion/sheet to emotion/css. **Motivation** During performance testing, it was revealed that creating a separate class for each component is slow. Rendering 10k elements <img width="269" alt="Снимок экрана 2023-10-05 в 13 34 12" src="https://github.com/appsmithorg/appsmith/assets/11555074/a881b188-b7d6-4fff-bc79-e7a81e37ffac"> As part of the task, an approach using styles through attributes was also tested, it works well, but we still need to create a separate class in runtime if we work with container queries. Because of this, I think it's best to use a ready-made solution from emotion/css, since it creates only one class out of the box for elements with the same styles, which allows to render elements with good performance. Rendering 80k elements ![Снимок экрана 2023-10-05 в 13 28 33](https://github.com/appsmithorg/appsmith/assets/11555074/510302f9-d45b-4b01-a59d-538d2f5d356e) #### PR fixes following issue(s) Fixes #27750 #### Type of change - Chore (housekeeping or task changes that don't impact user perception) ## Testing > #### How Has This Been Tested? > Please describe the tests that you ran to verify your changes. Also list any relevant details for your test configuration. > Delete anything that is not relevant - [x] Manual - [ ] JUnit - [x] Jest - [ ] Cypress ## Checklist: #### Dev activity - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [x] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag
2023-10-06 06:59:02 +00:00
"@emotion/css": "^11.11.2",
chore: add action group component (#29645) Fixes #29425 <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Introduced an icon alongside menu items, with positioning options. - Implemented a new `ActionGroup` component to manage a group of actions with overflow behavior and keyboard navigation. - Added new `ActionGroupItem` and `MoreIcon` components for action groups. - **Enhancements** - Improved resize handling in the `ThemeProvider` for conditional rendering based on measurements. - Updated button styles to adjust minimum inline sizing for better layout. - **Documentation** - Created Storybook stories to showcase `ActionGroup` configurations and usage. - **Style** - Modified list item styling in the `Menu` component to incorporate icons. - **Tests** - Added mock for `useDebounce` hook in `AppsmithIDE` tests. - Updated Cypress test assertions to accommodate changes in layout behavior. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Valera Melnikov <valera@appsmith.com>
2023-12-19 13:04:27 +00:00
"@react-aria/actiongroup": "^3.7.0",
chore: headless checkbox and styled checkbox component (#22380) Fixes #22142
2023-04-18 11:51:56 +00:00
"@react-aria/utils": "^3.16.0",
chore: Improve a11y of loading state of button (#23812) Fixes #23811
2023-05-30 12:37:49 +00:00
"@react-aria/visually-hidden": "^3.8.0",
chore: add action group component (#29645) Fixes #29425 <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Introduced an icon alongside menu items, with positioning options. - Implemented a new `ActionGroup` component to manage a group of actions with overflow behavior and keyboard navigation. - Added new `ActionGroupItem` and `MoreIcon` components for action groups. - **Enhancements** - Improved resize handling in the `ThemeProvider` for conditional rendering based on measurements. - Updated button styles to adjust minimum inline sizing for better layout. - **Documentation** - Created Storybook stories to showcase `ActionGroup` configurations and usage. - **Style** - Modified list item styling in the `Menu` component to incorporate icons. - **Tests** - Added mock for `useDebounce` hook in `AppsmithIDE` tests. - Updated Cypress test assertions to accommodate changes in layout behavior. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Valera Melnikov <valera@appsmith.com>
2023-12-19 13:04:27 +00:00
"@react-types/actiongroup": "^3.4.6",
chore: Refactor styled component to css modules for checkbox/radio/switch (#27505) Refactor css from styled component to css modules Fixed #27386 Fixed #27388 Fixed #27387
2023-09-22 07:14:58 +00:00
"clsx": "^2.0.0",
chore: improve buttonGroup (#27601) #### PR fixes following issue(s) Fixes #25500 #### Type of change - Chore (housekeeping or task changes that don't impact user perception) #### How Has This Been Tested? > Please describe the tests that you ran to verify your changes. Also list any relevant details for your test configuration. > Delete anything that is not relevant - [x] Manual - [ ] JUnit - [ ] Jest - [ ] Cypress ## Checklist: #### Dev activity - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [x] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag
2023-09-26 08:25:34 +00:00
"colorjs.io": "^0.4.3",
chore: Add tag group component (#29387) Fixes #29134 <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Introduced `TagGroup` and `Tag` components with features like label, description, error message, and tag removal options. - Added new stories for `TagGroup` to demonstrate various configurations and use cases. - **Enhancements** - Updated `Switch` component with improved validation logic. - Enhanced `TextArea` initialization to handle undefined default values more gracefully. - Added `validationState` property to `HelpText` and `Field` components to support form validation states. - **Style Updates** - Implemented new CSS styles for `TagGroup` and `Tag` components to improve UI consistency and interactivity. - **Documentation** - Expanded Storybook documentation with examples and usage guidelines for `TagGroup` and `Tag` components. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
2023-12-11 07:10:40 +00:00
"lodash": "*",
"react-aria-components": "^1.0.0-rc.0"
feat: wds button refactoring (#21849) ## Description 1. Moved `wds` to the `design-system` folder. 2. Added `headless` package and `HeadlessButton`. 3. Added `theming` package. `ThemeProvider` and two classes were created to work with tokens([TokensAccessor](https://github.com/appsmithorg/appsmith/pull/21849/files#diff-58832e8b8e8017648929473a90eb716e6a2671ba1749be3d4c5665b093bc3dc3)) and colors([ColorsAccessor](https://github.com/appsmithorg/appsmith/pull/21849/files#diff-f515e0eefc418c8bfc0710572e83a0029bd94f2fb975853f71730e5b11c774bd)) 5. The token structure has been changed. The same class(TokensAccessor) is now used to create CSS variables and tokens for Figma([themeTokens.json](https://github.com/appsmithorg/appsmith/pull/21849/files#diff-5ad75b848cb4254c0bd0bb0bf6a89eeccb628dc0012752172654e12e62d570d9)) The final storybook is [here](https://widget-design-system-b1p6g13iq-get-appsmith.vercel.app/?path=/story/design-system-widgets--button). ## Type of change - New feature (non-breaking change which adds functionality) - Chore (housekeeping or task changes that don't impact user perception) - This change requires a documentation update ## How Has This Been Tested? - Manual ## Checklist: ### Dev activity - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [x] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag --------- Co-authored-by: Valera Melnikov <melnikov.vv@greendatasoft.ru>
2023-04-05 12:39:11 +00:00
},
"devDependencies": {
fix: remove unnecessary packages dependency settings (#22736) ## Description We are for using the same version in packages as the main app. [This code](https://github.com/appsmithorg/appsmith/blob/release/app/client/packages/design-system/theming/package.json#L12-L19) should says yarn take the version from the main package.json. But for some reason, yarn resolves it in his own way, so we decided to delete these lines and leave only information about React only in `peerDependencies`. > Please delete options that are not relevant. - Bug fix (non-breaking change which fixes an issue) - Chore (housekeeping or task changes that don't impact user perception) ## How Has This Been Tested? - Manual ## Checklist: ### Dev activity - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag Co-authored-by: Valera Melnikov <melnikov.vv@greendatasoft.ru>
2023-04-27 06:25:14 +00:00
"eslint-plugin-storybook": "^0.6.10"
feat: wds button refactoring (#21849) ## Description 1. Moved `wds` to the `design-system` folder. 2. Added `headless` package and `HeadlessButton`. 3. Added `theming` package. `ThemeProvider` and two classes were created to work with tokens([TokensAccessor](https://github.com/appsmithorg/appsmith/pull/21849/files#diff-58832e8b8e8017648929473a90eb716e6a2671ba1749be3d4c5665b093bc3dc3)) and colors([ColorsAccessor](https://github.com/appsmithorg/appsmith/pull/21849/files#diff-f515e0eefc418c8bfc0710572e83a0029bd94f2fb975853f71730e5b11c774bd)) 5. The token structure has been changed. The same class(TokensAccessor) is now used to create CSS variables and tokens for Figma([themeTokens.json](https://github.com/appsmithorg/appsmith/pull/21849/files#diff-5ad75b848cb4254c0bd0bb0bf6a89eeccb628dc0012752172654e12e62d570d9)) The final storybook is [here](https://widget-design-system-b1p6g13iq-get-appsmith.vercel.app/?path=/story/design-system-widgets--button). ## Type of change - New feature (non-breaking change which adds functionality) - Chore (housekeeping or task changes that don't impact user perception) - This change requires a documentation update ## How Has This Been Tested? - Manual ## Checklist: ### Dev activity - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [x] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag --------- Co-authored-by: Valera Melnikov <melnikov.vv@greendatasoft.ru>
2023-04-05 12:39:11 +00:00
},
"peerDependencies": {
"react": "^16.8.0 || ^17.0.0-rc.1 || ^18.0.0"
chore: Yarn workspaces + Storybook + WDS (#20776)
2023-03-03 06:47:35 +00:00
}
}
Reference in New Issue Copy Permalink