- Acme -
-- Pages in Storybook -
-- We recommend building UIs with a - - - - component-driven - - - - process starting with atomic components and ending with pages. -
-- Render pages with mock data. This makes it easy to build and review page states without needing to navigate to them in your app. Here are some handy patterns for managing page data in Storybook: -
--
-
- - Use a higher-level connected component. Storybook helps you compose such data from the "args" of child component stories - -
- - Assemble data in the page component from your services. You can mock these services out using Storybook. - -
- Get a guided tutorial on component-driven development at - - - Learn Storybook - - . Read more in the - - - docs - - . -
- Acme -
-- Pages in Storybook -
-- We recommend building UIs with a - - - - component-driven - - - - process starting with atomic components and ending with pages. -
-- Render pages with mock data. This makes it easy to build and review page states without needing to navigate to them in your app. Here are some handy patterns for managing page data in Storybook: -
--
-
- - Use a higher-level connected component. Storybook helps you compose such data from the "args" of child component stories - -
- - Assemble data in the page component from your services. You can mock these services out using Storybook. - -
- Get a guided tutorial on component-driven development at - - - Learn Storybook - - . Read more in the - - - docs - - . -
--
+
-
- {props.selectedFsEnties.map((e: FsEntity) => {
+ {props.selectedFsEntities.map((e: FsEntity) => {
return (
- - Selected {props.selectedFsEnties.length} file - {props.selectedFsEnties.length > 1 ? "s" : ""} + Selected {props.selectedFsEntities.length} file + {props.selectedFsEntities.length > 1 ? "s" : ""}
relative Path | +New Name | +
+ {isFolders ? "Merge" : "Overwrite"}
+ |
+
---|
+ Folders that would be merged: + {changeNamesOrOverwriteTable(foldersToMerge, true)} +
+ )} + {!!filesToOverwrite.length && ( ++ Files that would be overwritten: + {changeNamesOrOverwriteTable(filesToOverwrite, false)} +
+ )} + {(!!entitiesWithInvalidName.length || !!insufficientPermission.length) && ( ++ Files that must be renamed: + {changeNamesOrOverwriteTable([...entitiesWithInvalidName,...insufficientPermission], false)} +
+ )} +Drop files here ...
+ ) : ( +Drag 'n' drop files or folders here, or click to select files
+ )} +Acme
-src/storybook-examples/welcome.mdx
-Pages in Storybook
-- We recommend building UIs with a{' '} - - component-driven - {' '} - process starting with atomic components and ending with pages. -
-- Render pages with mock data. This makes it easy to build and review page states without - needing to navigate to them in your app. Here are some handy patterns for managing page data - in Storybook: -
--
-
- - Use a higher-level connected component. Storybook helps you compose such data from the - "args" of child component stories - -
- - Assemble data in the page component from your services. You can mock these services out - using Storybook. - -
- Get a guided tutorial on component-driven development at{' '} - - Learn Storybook - - . Read more in the{' '} - - docs - - . -
-