kasperskylab / uif Goto Github PK

Good DX, minimum tooling set and unified rules for forms with business logic.

@kaspersky/form-builder + Storybook = ❤️

Currently @kaspersky/components uses styled-components and Provider to switch between light and dark theme.

It would be the same quality and more perfomant to use css-only solution like so:

1. design tokens defined as css-variables;
2. theme switching by data attribute and cascade.

Packages @kaspersky/components, @kaspersky/dev-tools and other should be auto-published after merging PR.

Add package @kl/components.graph and it's shared storybook.

Add package @kl/icons and it's shared storybook.

It is more useful to get quick start information in each package README file:

• components-v6
• runtime
• ui-builder
• dev-tools

It will very helpful to add typings for UI Builder.
For 3 reasons:

1. For users (developers) — they get types for each handler type etc.
2. For maintainers — it will be more predictable to work with current code.
3. Also it unblocks the next step — @kaspersky/form-builder. Tool to build UI forms from typed code.

It would be more interesting to see the real case of UIF usage with an illustrated example like pic below:

Form plan and do it :)

Replace AntD usages to simplify @kaspersky/components usage and maintenance.

Tests is running with Jest & Puppeteer. Tests is placed in ./screenshots. Tests are run via docker-compose.

Typo in kl-components-v6/README.

Add key info about UIF:

• Benefits
• Platform description and integration scenarios
• Quick Start section

• @kaspersky/runtime
• @kaspersky/ui-builder
• @kaspersky/dev-tools
• @kaspersky/components

I'm trying to install dependencies in ui-builder but I'm getting the error

https://registry.npmjs.org/image-size/image-size-0.5.5.tgz: Request failed "405 Method Not Allowed"

Link to package in yarn.lock: https://registry.npmjs.org/interpret/interpret-1.2.0.tgz#d5061a6224be58e8083985f5014d844359576296

Correct link: https://registry.npmjs.org/interpret/-/interpret-1.2.0.tgz#d5061a6224be58e8083985f5014d844359576296

This is not the only package with a broken link

• Base Navigation
• Hamburger mode
• Links example
• Fix click on item without subs
• Expand 2nd and 3rd lvl in collapsed and expanded modes
• User menu in footer
• badge / counter for menu items
• pin items

@kaspersky/form-builder must be based on the rich experience of @kaspersky/ui-builder but also it should be the next generation step including at least 4 key points:

1. form builds from code;
2. fully typed;
3. only one way to do something (including data layer);
4. no gap with @kaspersky/components or other UI Kits

Also new library should keep UI Builder feature: DSL.

It needs to build and publish Storybook after merging PR.
It can be deployed to Vercel, Netlify or Github pages.

I'm trying to build a docker image for ui-builder but I'm getting an error:

#0 0.424 warning Skipping preferred cache folder "/.cache/yarn" because it is not writable.
#0 0.424 warning Selected the next writable cache folder in the list, will be "/tmp/.yarn-cache-1001".
#0 0.431 error An unexpected error occurred: "EACCES: permission denied, open '/.yarnrc'".

Instead of ./packages/packages/kl-components/v6/ it might be ./packages/kl-components-v6/.
I.e. duplicate packages section

package.json (ui-builder) contains dependencies @kl/components-v6, @kl/dev-tools, @kl/runtime that can't be installed.

[2/4] Fetching packages...
error An unexpected error occurred: "https://registry.npmjs.org/@kl/components-v6/-/@kl/-/components-v6-0.24.2.tgz: Request failed \"404 Not Found\"".

Add a Changelog:

1. by conventional commits,
2. github releases,
3. and do it like Node.js or NothingOS.

UIF has several scenarios:

• Cross package updates, i.e. dependencies and versioning
• Auto-publish on merging to main branch
• Tests, linting

Now UIF uses obsolete Lerna version and it can be right way to update to Nx + latest Lerna.
Also, it might be easier and more efficient to avoid using Lerna and get tiny tools for release management.