@luscii-healthtech/web-ui 0.0.0-alpha.caf5372 → 0.0.0-dynamic

package/README.md

@@ -1,23 +1,23 @@
-# web-ui
+# WebUI
 
-The web-ui repository contains the web UI components for Luscii's front end projects. It is published to NPM for inclusion into our projects. It also uses storybook and is published to chromatic for easy review of changes.
+The `web-ui` repository contains the UI components for Luscii's frontend projects. It is published to NPM for usage into our projects. It uses Storybook and is published to Chromatic for easy review and tracking of visual changes.
 
 ## Running locally
 
-If you want to run storybook locally you can use
+If you want to run Storybook locally you can use:
 
 ```bash
 yarn install
-yarn storybook
+yarn dev # runs a Tailwind watcher and Storybook
 ```
 
 ## Testing your production build
 
 Assuming the following setup:
 
-- The `web-ui` and `cVitals-Web` repositories are siblings are in the same folder
-- You have ran `yarn install` on `cVitals-Web`
-- You have ran `yarn build` on `web-ui`
+- The `web-ui` and `cVitals-Web` repositories are siblings in the same folder.
+- You ran `yarn install` in `cVitals-Web`.
+- You ran `yarn build` in `web-ui`.
 
 Run the script below in your terminal, _in the parent folder of the repositories_.
 
@@ -31,79 +31,149 @@ Or use the shortcut:
 yarn test-copy-build
 ```
 
-When you run cVitals again, it should contain your latest updates in the component library. Use this to make sure your changes are solid before merging a pull request.
+When you run `cVitals-Web` again, it should contain your latest updates in the component library. Use this to make sure your changes are solid before opening a pull request.
 
 ## Contributing
 
-Make sure you understand our design system and follow its guidelines. They are document in storybook. We value consistency, simplicity and usability highly. Don't mess it up.
+Thank you for your help in keeping our component library organized and easy to use!
 
-If you want to add components, do so in
+When adding components, please make sure to implement them consistently in our projects and that it is clear where and when they should be used. We want to avoid having many similar components. If you want to add components, do so in the `/src/components` directory. When you create new components, add them to Storybook as well. Stories go in the `/stories` directory.
 
-```
-/src/components
-```
+If you add new components, please make sure they fit in with our existing ones and that it's clear where and when they should be used. We want to avoid having too many similar components.
 
-Please stay vigilant when adding components that we implement them consistently in our projects and that it is clear when and where they have to be used. We want to avoid a lot of components that are similar.
+### Documentation
 
-When you create new components, you must add them to storybook as well. Stories go in
+Every component should have proper documentation that explains when, where and how to use it. This sounds like a lot of work, but it doesn't have to be. And it's important, also for you, to quickly see how to best use a component.
 
+Component documentation should include the following parts:
+
+- A short explanation of each prop in a JSDoc comment style.
+- A stories file (`<ComponentName>.stories.tsx`).
+- A docs file (`<ComponentName>.docs.mdx`).
+
+Below is an explanation of each.
+
+#### Props documented via JSDoc comments
+
+A short explanation of each prop in a JSDoc comment style. These will show up in your IDE for on the fly documentation when you need it. It will also show up in Storybook, so this is a double-whammy and provides documentation exactly where you need it.
+
+```ts
+type Props = {
+  /**
+   * Optional description that will be shown close to the label, used to provide more
+   * detail about the field next to the concise text of the label.
+   */
+  helperText?: string;
+};
 ```
-/stories
-```
+
+#### Stories file
+
+Stories files (`*stories.tsx`) will show up in Storybook as separate entries/pages for each component. Each component can have multiple stories defined for it, showing different use cases, variants and states of that component.  
+It is important to include stories for a lot of these different variants and states, because visual snapshots will be created of these stories by a tool called Chromatic. This allows us to visually track changes to the component over time, and ensure that it looks and behaves correctly across different use cases. By writing stories that showcase all the different ways your component can be used, you can catch issues early and ensure that your component is robust and reliable.
+
+You can find the Chromatic project for WebUI [here](https://www.chromatic.com/library?appId=62b0c4d5afd432f7ee70a740).
+
+#### Docs file
+
+The component docs file brings everything together and should be considered the source of truth about the component. What should be documented:
+
+- Why we have the component and where it should be used.
+- An overview of the different variants and states.
+- Usage guidelines of when and where to use the component.
+- Best practices to show what to do and what not do when working with the component.
+
+> 🔎 If you need to e.g. create a story to show how NOT to use a component, you might not want
+> to create a snapshot for that component or show it in the sidebar of Storybook. To omit a story
+> from snapshots, add the following to its parameters:
+>
+> ```ts
+> chromatic: { disableSnapshot: true },
+> ```
+>
+> To hide a story from the sidebar, prefix the story (variable) name
+> with `HIDE_`.
+
+Please see examples of other components' docs files for inspiration and try to stay consistent with how they are documented.
+
+### Accessibility
+
+WebUI is not currently designed to support screen reader usage. This is because our application is designed specifically for healthcare providers and is not publicly accessible. Our primary users are caregivers who work in healthcare and do not rely on screen readers to be able to use our application.  
+However, it is important for developers to write accessible frontend code. Even if our current application is not designed to support screen reader usage. This means following best practices for web accessibility, such as using semantic HTML, providing alternative text for images, and ensuring keyboard navigation is possible. While our primary users may not rely on screen readers, it is important to make our application as inclusive as possible to all users.
+
+### Testing
+
+WebUI relies on two types of testing: Visual snapshot testing via Chromatic and interaction testing via Storybook.
+
+Visual snapshot testing is handled for you. Any story you write will be picked up by Chromatic and it will create a snapshot for it.
+
+Interaction testing via Storybook allows to programmatically interact with the component. This is very helpful in testing any logic that the component may use internally and any states of the component that might be hard/impossible to trigger from the outside.  
+More information on how to approach writing interaction tests can be found in [this page of the Storybook documentation](https://storybook.js.org/docs/react/writing-tests/interaction-testing#write-an-interaction-test).
 
 ### Adding icons
 
-Add new icons by:
+Add new icons by following these steps:
 
-- Add the svg file(s) in `src/components/Icons/icons`
-- Run `yarn icons`
+- Add the svg file(s) in `src/components/Icons/icons`.
+- Run `yarn icons`.
 
 The icons are optimized by SVGO and transformed into React components by [SVGR](https://react-svgr.com) which are placed in `src/components/Icons`.
 
 ## CI setup
 
-#### Branching
+### Branching
 
-The `main` branch is our default branch. When you contribute, branch from there and name your branch
+The `main` branch is our default branch. When you contribute, branch from there and use the following branch naming convention:
 
 ```
-  //Branch names convention (enforced)
+  // Branch naming convention (enforced)
 
-  major/*      //for a new design system or changes that effect our foundations (typography, color)
-  minor/*      //for new components and stories
-  patch/*      //for small improvements to existing components, stories
-  bug/*        //for bugs, fixes
+  major/*      // For a new design system or changes that effect our foundations (e.g. typography, color).
+  minor/*      // For new components and stories.
+  patch/*      // For small improvements to existing components or stories.
+  bug/*        // For bugs or fixes.
+  chore/*      // For things related to development that don't impact the output for consumers and/or users.
 ```
 
 We have configured at lot of magic for your convenience.
 
-#### On every PR
+### On every PR
 
-1. the module build, lint and tests are checked.
-2. The storybook build is published to chromatic.
+1. The module build, lint and tests are checked.
+2. The Storybook build is published to Chromatic.
 3. Labels are added based on the branch name and PR size.
-4. Branch names must follow the convention and are checked
-
-#### On merge to main
+4. Branch names must follow the convention and are checked.
 
-1. Draft a github release
-2. Version bump of the package
-3. Publish new package to NPM
+### On merge to main
 
----
+1. Drafts a GitHub release.
+2. Bumps the version of the package.
+3. Publishes the new package version to NPM.
 
-## IE11
+## Stories
 
-This package includes [dnd-kit](https://dndkit.com) as a peer dependency. The bundle of dnd-kit contains syntax which isn't compatible with IE11, therefore any application needing to support IE11 has to transpile dnd-kit.
+### Stories using deprecated props
 
-It should also at least include the following polyfills to make it work:
+When creating new stories for components with deprecated functionality please prefix the story name with `Deprecated`. In addition, also mark it with a "DEPRECATED" badge via the story's parameters.
 
-- [core-js](https://www.npmjs.com/package/core-js)
-- [regenerator-runtime](https://www.npmjs.com/package/regenerator-runtime)
-- [smoothscroll-polyfill](https://www.npmjs.com/package/smoothscroll-polyfill)
+For example a story of a `FullPageModal` component using the deprecated `primaryButtonProps` prop would look like this:
 
-Optional:
+```tsx
+import { BADGES } from "../.storybook/constants";
 
-- [web-animations-js](https://www.npmjs.com/package/web-animations-js)
+export const DeprecatedWithPrimaryButtonProps = {
+  render: OneColumTemplate,
+  args: {
+    isOpen: true,
+    primaryButtonProps: {
+      onClick: action("onClick Primary Button"),
+      text: "Primary",
+    },
+  },
+  parameters: {
+    badges: [BADGES.DEPRECATED],
+  },
+};
+```
 
-This isn't necessary if the [drop animation is disabled](https://github.com/clauderic/dnd-kit/issues/705#issuecomment-1103056336). Check out [this ticket](https://github.com/clauderic/dnd-kit/issues/271) for more information on IE11.
+This groups deprecated stories together and will make it easier to remove them later on.

package/dist/components/Accordion/Accordion.d.ts

@@ -1,11 +1,10 @@
-import p from "react";
-declare const I: ({ dataTestId: a, isCollapsedByDefault: o, items: r, className: i }: {
-    dataTestId: any;
-    isCollapsedByDefault?: boolean | undefined;
-    items: any;
-    className: any;
-}) => p.DetailedReactHTMLElement<{
-    "data-test-id": any;
-    className: any;
-}, HTMLElement>;
-export default I;
+import React from "react";
+import { AccordionItemProps } from "./AccordionItem";
+export interface AccordionProps {
+    dataTestId?: string;
+    items: AccordionItemProps[];
+    className?: string;
+    isCollapsedByDefault?: boolean;
+}
+declare const Accordion: React.VFC<AccordionProps>;
+export default Accordion;

package/dist/components/Accordion/AccordionItem.d.ts

@@ -1,10 +1,9 @@
-import e from "react";
-export declare const AccordionItem: ({ id: t, title: s, content: i, isCollapsedByDefault: l }: {
-    id: any;
-    title: any;
-    content: any;
-    isCollapsedByDefault?: boolean | undefined;
-}) => e.DetailedReactHTMLElement<{
-    className: string;
-    "data-test-id": any;
-}, HTMLElement>;
+import React from "react";
+export interface AccordionItemProps {
+    id: string | number;
+    title: string;
+    content: React.ReactNode;
+    className?: string;
+    isCollapsedByDefault?: boolean;
+}
+export declare const AccordionItem: React.VFC<AccordionItemProps>;

package/dist/components/AccordionList/AccordionList.d.ts

@@ -1,5 +1,42 @@
-import n from "react";
-export declare const AccordionList: (z: any) => n.DetailedReactHTMLElement<{
-    className: string;
-}, HTMLElement>;
-export default AccordionList;
+import React from "react";
+import { AccordionProps } from "../Accordion/Accordion";
+import { DraggableListProps, ListItemProps, SortableListProps } from "../List/List.types";
+import { AccordionItemProps } from "../Accordion/AccordionItem";
+import { BaseButtonProps } from "../ButtonV2/ButtonProps.type";
+import { AccordionListActions } from "./subcomponents/AccordionListActions";
+export interface AccordionListProps extends Omit<AccordionProps, "items"> {
+    localisations: {
+        title: string;
+        searchPlaceholder?: string;
+        emptyListText?: string;
+    };
+    accordionItems: AccordionItem[];
+    /**
+     * @deprecated
+     * Use the `actions` prop to render any button(s)
+     * or other component(s) automatically in the correct area.
+     */
+    buttonProps?: BaseButtonProps;
+    isSearchEnabled?: boolean;
+    isLoading?: boolean;
+    actions?: React.ReactNode;
+}
+export type AccordionListItemProps<T = ListItemProps> = Omit<AccordionItemProps, "content"> & {
+    listItems: T[];
+    draggableListType?: "default";
+};
+export type DraggableAccordionListItemProps = Omit<AccordionItemProps, "content"> & {
+    draggableListType: "draggable";
+    listItems: DraggableListProps["items"];
+};
+export type SortableAccordionListItemProps = Omit<AccordionItemProps, "content"> & {
+    draggableListType: "sortable";
+    draggableIdentifier: string;
+    listItems: SortableListProps["items"];
+};
+export type AccordionItem = AccordionListItemProps | DraggableAccordionListItemProps | SortableAccordionListItemProps;
+interface StaticComponents {
+    Actions: typeof AccordionListActions;
+}
+export declare const AccordionList: React.FC<AccordionListProps> & StaticComponents;
+export default AccordionList;

package/dist/components/AccordionList/subcomponents/AccordionListActions.d.ts

@@ -0,0 +1,18 @@
+import React from "react";
+/**
+ * Use in the actions of an AccordionList. Spaces out the action
+ * components correctly in relation to the styling of the AccordionList component.
+ *
+ * @usage
+ * ```tsx
+ * <AccordionList
+ *   actions={
+ *     <AccordionList.Actions>
+ *       <PrimaryButton />
+ *       <SecondaryButton />
+ *     </AccordionList.Actions>
+ *   }
+ * />
+ * ```
+ */
+export declare const AccordionListActions: React.FC<React.PropsWithChildren>;

package/dist/components/Badge/Badge.d.ts

@@ -1,5 +1,7 @@
-import s from "react";
-declare const o: (e: any) => s.DetailedReactHTMLElement<{
-    className: string;
-}, HTMLElement>;
-export default o;
+/// <reference types="react" />
+interface BadgeProps {
+    badgeCount: number;
+    className?: string;
+}
+declare const Badge: (props: BadgeProps) => JSX.Element;
+export default Badge;

package/dist/components/BaseList/BaseList.d.ts

@@ -1,13 +1,7 @@
-import o from "react";
-export declare const BaseList: o.ForwardRefExoticComponent<{
-    dataTestId: any;
-    title: any;
-    headerButton: any;
-    emptyStateMessage: any;
-    isLoading: any;
-    items: any;
-    headerTransparent: any;
-    itemComponent: any;
-    footer: any;
-    withBorder?: boolean | undefined;
-} & o.RefAttributes<unknown>>;
+import React from "react";
+import type { BaseListItemProps, BaseListProps } from "./BaseList.types";
+declare const BaseListInner: <T extends BaseListItemProps>({ dataTestId, title, headerButton, emptyStateMessage, isLoading, items, headerTransparent, itemComponent, footer, withBorder, }: BaseListProps<T>, ref: React.ForwardedRef<HTMLUListElement>) => JSX.Element;
+export declare const BaseList: <T extends BaseListItemProps>(props: BaseListProps<T> & {
+    ref?: React.ForwardedRef<HTMLUListElement> | undefined;
+}) => ReturnType<typeof BaseListInner>;
+export {};

package/dist/components/BaseList/BaseList.types.d.ts

@@ -1,55 +1,55 @@
-import React, { Ref, ReactNode } from "react";
-import { PrimaryButtonProps } from "../..";
-import { ButtonDefinition } from "../ButtonV2/ButtonProps.type";
-import { IconProps } from "../Icons/types/IconProps.type";
-import { TitleProps } from "../Title/Title";
-export type BaseListItemProps = {
-    itemId: string | number;
-    title: string;
-    subtitle?: string;
-    icon?: React.FunctionComponent<IconProps> | string;
-    accessories?: JSX.Element[];
-    onClick?: (e: React.MouseEvent<HTMLLIElement>) => void;
-    /** Same as onClick to be compatible with listItem */
-    handleItemClick?: (e: React.MouseEvent<HTMLLIElement>) => void;
-    onAssetLoadError?: (payload: OnAssetLoadErrorPayload) => void;
-    tooltipId?: string;
-    isSelected?: boolean;
-    roundTop?: boolean;
-    roundBottom?: boolean;
-    withBorder?: boolean;
-    isDraggable?: boolean;
-    dataTestId?: string;
-    ref?: Ref<HTMLLIElement>;
-    renderDragHandle?: () => ReactNode;
-    htmlProps?: React.HTMLProps<HTMLLIElement>;
-};
-export type OnAssetLoadErrorPayload = Pick<BaseListItemProps, "itemId" | "subtitle" | "title" | "icon">;
-export interface BaseListProps<T extends BaseListItemProps = BaseListItemProps> {
-    items: T[];
-    title?: string | TitleProps;
-    headerButton?: ButtonDefinition<PrimaryButtonProps>;
-    headerTransparent?: boolean;
-    itemComponent?: React.FC<T>;
-    emptyStateMessage?: string;
-    isLoading?: boolean;
-    dataTestId?: string;
-    footer?: ReactNode;
-    withBorder?: boolean;
-    ref?: Ref<HTMLUListElement>;
-}
-export type BaseListHeaderProps = {
-    title?: string | TitleProps;
-    button?: ButtonDefinition<PrimaryButtonProps>;
-    transparent?: boolean;
-    withBorder?: boolean;
-};
-export type DraggableBaseListProps = Omit<BaseListProps<DraggableBaseListItemProps>, "itemComponent">;
-export type DraggableBaseListItemProps = BaseListItemProps & {
-    draggableIdentifier: string;
-    draggableData?: Record<string, unknown>;
-};
-export type SortableBaseListProps = DraggableBaseListProps & {
-    draggableIdentifier: string;
-};
-export type SortableBaseListItemProps = DraggableBaseListItemProps;
+import React, { Ref, ReactNode } from "react";
+import { PrimaryButtonProps } from "../..";
+import { ButtonDefinition } from "../ButtonV2/ButtonProps.type";
+import { IconProps } from "../Icons/types/IconProps.type";
+import { TitleProps } from "../Title/Title";
+export type BaseListItemProps = {
+    itemId: string | number;
+    title: string;
+    subtitle?: string;
+    icon?: React.FunctionComponent<IconProps> | string;
+    accessories?: JSX.Element[];
+    onClick?: (e: React.MouseEvent<HTMLLIElement>) => void;
+    /** Same as onClick to be compatible with listItem */
+    handleItemClick?: (e: React.MouseEvent<HTMLLIElement>) => void;
+    onAssetLoadError?: (payload: OnAssetLoadErrorPayload) => void;
+    tooltipId?: string;
+    isSelected?: boolean;
+    roundTop?: boolean;
+    roundBottom?: boolean;
+    withBorder?: boolean;
+    isDraggable?: boolean;
+    dataTestId?: string;
+    ref?: Ref<HTMLLIElement>;
+    renderDragHandle?: () => ReactNode;
+    htmlProps?: React.HTMLProps<HTMLLIElement>;
+};
+export type OnAssetLoadErrorPayload = Pick<BaseListItemProps, "itemId" | "subtitle" | "title" | "icon">;
+export interface BaseListProps<T extends BaseListItemProps = BaseListItemProps> {
+    items: T[];
+    title?: string | TitleProps;
+    headerButton?: ButtonDefinition<PrimaryButtonProps>;
+    headerTransparent?: boolean;
+    itemComponent?: React.FC<T>;
+    emptyStateMessage?: string;
+    isLoading?: boolean;
+    dataTestId?: string;
+    footer?: ReactNode;
+    withBorder?: boolean;
+    ref?: Ref<HTMLUListElement>;
+}
+export type BaseListHeaderProps = {
+    title?: string | TitleProps;
+    button?: ButtonDefinition<PrimaryButtonProps>;
+    transparent?: boolean;
+    withBorder?: boolean;
+};
+export type DraggableBaseListProps = Omit<BaseListProps<DraggableBaseListItemProps>, "itemComponent">;
+export type DraggableBaseListItemProps = BaseListItemProps & {
+    draggableIdentifier: string;
+    draggableData?: Record<string, unknown>;
+};
+export type SortableBaseListProps = DraggableBaseListProps & {
+    draggableIdentifier: string;
+};
+export type SortableBaseListItemProps = DraggableBaseListItemProps;

package/dist/components/BaseList/BaseListEmptyState.d.ts

@@ -1,9 +1,7 @@
-import e from "react";
-export declare const BaseListEmptyState: ({ message: t, roundTop: o, withBorder: r }: {
-    message: any;
-    roundTop: any;
-    withBorder: any;
-}) => e.DetailedReactHTMLElement<{
-    className: string;
-}, HTMLElement>;
-export default BaseListEmptyState;
+import React from "react";
+export declare const BaseListEmptyState: React.FC<{
+    message: string;
+    roundTop?: boolean;
+    withBorder?: boolean;
+}>;
+export default BaseListEmptyState;

package/dist/components/BaseList/BaseListHeader.d.ts

@@ -1,11 +1,4 @@
-import p from "react";
-export declare const BaseListHeader: ({ title: s, button: e, transparent: r, withBorder: o }: {
-    title: any;
-    button: any;
-    transparent: any;
-    withBorder: any;
-}) => p.DetailedReactHTMLElement<{
-    "data-test-id": string;
-    className: string;
-}, HTMLElement>;
-export default BaseListHeader;
+import React from "react";
+import type { BaseListHeaderProps } from "./BaseList.types";
+export declare const BaseListHeader: React.FC<BaseListHeaderProps>;
+export default BaseListHeader;

package/dist/components/BaseList/BaseListIcon.d.ts

@@ -1,7 +1,5 @@
-import o from "react";
-export declare const BaseListIcon: ({ icon: t, onAssetLoadError: e }: {
-    icon: any;
-    onAssetLoadError: any;
-}) => o.FunctionComponentElement<{
-    children?: o.ReactNode;
-}>;
+import React from "react";
+import { BaseListItemProps } from "./BaseList.types";
+export declare const BaseListIcon: React.FC<Pick<BaseListItemProps, "icon"> & {
+    onAssetLoadError?: () => void;
+}>;

package/dist/components/BaseList/BaseListItem.d.ts

@@ -1,3 +1,4 @@
-import s from "react";
-export declare const BaseListItem: s.ForwardRefExoticComponent<s.RefAttributes<unknown>>;
-export default BaseListItem;
+import React from "react";
+import type { BaseListItemProps } from "./BaseList.types";
+export declare const BaseListItem: React.FC<BaseListItemProps>;
+export default BaseListItem;

package/dist/components/BaseList/DraggableBaseList/DraggableBaseList.d.ts

@@ -1,14 +1,4 @@
-import b from "react";
-export declare const DraggableBaseList: (r: any) => b.FunctionComponentElement<{
-    dataTestId: any;
-    title: any;
-    headerButton: any;
-    emptyStateMessage: any;
-    isLoading: any;
-    items: any;
-    headerTransparent: any;
-    itemComponent: any;
-    footer: any;
-    withBorder?: boolean | undefined;
-} & b.RefAttributes<unknown>>;
-export default DraggableBaseList;
+import React from "react";
+import type { DraggableBaseListProps } from "../BaseList.types";
+export declare const DraggableBaseList: React.FC<DraggableBaseListProps>;
+export default DraggableBaseList;

package/dist/components/BaseList/DraggableBaseList/DraggableBaseListItem.d.ts

@@ -1,2 +1,3 @@
-import d from "react";
-export declare const DraggableBaseListItem: (r: any) => d.FunctionComponentElement<d.RefAttributes<unknown>>;
+import React from "react";
+import { DraggableBaseListItemProps } from "../BaseList.types";
+export declare const DraggableBaseListItem: React.FC<DraggableBaseListItemProps>;

package/dist/components/BaseList/DraggableBaseList/index.d.ts

@@ -1,2 +1,2 @@
-export { DraggableBaseList } from "./DraggableBaseList";
-export { DraggableBaseListItem } from "./DraggableBaseListItem";
+export { DraggableBaseList } from "./DraggableBaseList";
+export { DraggableBaseListItem } from "./DraggableBaseListItem";

package/dist/components/BaseList/ListSkeleton/ListItemSkeleton.d.ts

@@ -1,4 +1,2 @@
-import e from "react";
-export declare const ListItemSkeleton: () => e.DetailedReactHTMLElement<{
-    className: string;
-}, HTMLElement>;
+/// <reference types="react" />
+export declare const ListItemSkeleton: () => JSX.Element;

package/dist/components/BaseList/ListSkeleton/ListSkeleton.d.ts

@@ -1,9 +1,8 @@
-import e from "react";
-import "./ListSkeleton.scss";
-export declare const ListSkeleton: ({ items: t, dataTestId: s }: {
-    items: any;
-    dataTestId?: string | undefined;
-}) => e.DetailedReactHTMLElement<{
-    "data-test-id": string;
-    className: string;
-}, HTMLElement>;
+/// <reference types="react" />
+import "./ListSkeleton.scss";
+type ListSkeletonProps = {
+    items: number;
+    dataTestId?: string;
+};
+export declare const ListSkeleton: ({ items, dataTestId, }: ListSkeletonProps) => JSX.Element;
+export {};

package/dist/components/BaseList/SortableBaseList/SortableBaseList.d.ts

@@ -1,3 +1,4 @@
-import f from "react";
-export declare const SortableBaseList: (o: any) => f.DetailedReactHTMLElement<f.InputHTMLAttributes<HTMLInputElement>, HTMLInputElement>;
-export default SortableBaseList;
+import React from "react";
+import type { SortableBaseListProps } from "../BaseList.types";
+export declare const SortableBaseList: React.FC<SortableBaseListProps>;
+export default SortableBaseList;

package/dist/components/BaseList/SortableBaseList/SortableBaseListItem.d.ts

@@ -1,7 +1,3 @@
-import i from "react";
-export declare const SortableBaseListItem: (a: any) => i.FunctionComponentElement<i.RefAttributes<unknown>> | i.DetailedReactHTMLElement<{
-    style: {
-        transform: string | undefined;
-        position: "relative";
-    };
-}, HTMLElement>;
+import React from "react";
+import { SortableBaseListItemProps } from "../BaseList.types";
+export declare const SortableBaseListItem: React.FC<SortableBaseListItemProps>;

package/dist/components/BaseList/SortableBaseList/index.d.ts

@@ -1,2 +1,2 @@
-export { SortableBaseList } from "./SortableBaseList";
-export { SortableBaseListItem } from "./SortableBaseListItem";
+export { SortableBaseList } from "./SortableBaseList";
+export { SortableBaseListItem } from "./SortableBaseListItem";