@wix/patterns 1.468.0 → 1.469.0

package/dist/{docs → examples}/CustomFieldType/add-field-modal.tsx

@@ -1,3 +1,9 @@
+/**
+ * Illustrative example for `CustomFieldType` — see `dist/docs/CustomFieldType.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ */
 import React from 'react';
 import { CollectionPage } from '@wix/patterns/page';
 import { EditableTable, defineFieldType } from '@wix/patterns';

package/dist/{docs → examples}/CustomFieldType/editable-cell.tsx

@@ -1,3 +1,9 @@
+/**
+ * Illustrative example for `CustomFieldType` — see `dist/docs/CustomFieldType.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ */
 import React from 'react';
 import { CollectionPage } from '@wix/patterns/page';
 import { EditableTable, defineFieldType } from '@wix/patterns';

package/dist/{docs → examples}/CustomFieldType/entity-page-form.tsx

@@ -1,3 +1,9 @@
+/**
+ * Illustrative example for `CustomFieldType` — see `dist/docs/CustomFieldType.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ */
 import React from 'react';
 import { defineFieldType } from '@wix/patterns';
 import type { Field, FormFieldComponentProps } from '@wix/patterns';

package/dist/{docs → examples}/CustomFieldType/table-cell-and-filter.tsx

@@ -1,3 +1,9 @@
+/**
+ * Illustrative example for `CustomFieldType` — see `dist/docs/CustomFieldType.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ */
 import React from 'react';
 import { CollectionPage } from '@wix/patterns/page';
 import {

package/dist/{docs → examples}/CustomFieldsWidget/basic.tsx

@@ -1,3 +1,15 @@
+/**
+ * Illustrative example for `CustomFieldsWidget` — see `dist/docs/CustomFieldsWidget.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ *
+ * These imports are environment-scoped — they resolve only against a Wix
+ * build environment (a Yoshi flow runtime, a generated service client, an
+ * internal sibling) and are NOT needed to use the component. Substitute
+ * your own:
+ *   @wix/ambassador-cairo-dummyservice-v1-dummy-entity/types
+ */
 import React from 'react';
 import { CustomFieldsWidget } from '@wix/patterns';
 import { Button, Cell, Layout, Loader, Page } from '@wix/design-system';

package/dist/{docs → examples}/CustomFieldsWidget/controllable-state.tsx

@@ -1,3 +1,15 @@
+/**
+ * Illustrative example for `CustomFieldsWidget` — see `dist/docs/CustomFieldsWidget.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ *
+ * These imports are environment-scoped — they resolve only against a Wix
+ * build environment (a Yoshi flow runtime, a generated service client, an
+ * internal sibling) and are NOT needed to use the component. Substitute
+ * your own:
+ *   @wix/ambassador-cairo-dummyservice-v1-dummy-entity/types
+ */
 import React from 'react';
 import {
   CustomFieldsWidget,

package/dist/{docs → examples}/CustomFieldsWidget/empty-state.tsx

@@ -1,3 +1,9 @@
+/**
+ * Illustrative example for `CustomFieldsWidget` — see `dist/docs/CustomFieldsWidget.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ */
 /* eslint-disable import/no-extraneous-dependencies */
 
 import React from 'react';

package/dist/{docs → examples}/CustomFieldsWidget/inline-theme.tsx

@@ -1,3 +1,15 @@
+/**
+ * Illustrative example for `CustomFieldsWidget` — see `dist/docs/CustomFieldsWidget.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ *
+ * These imports are environment-scoped — they resolve only against a Wix
+ * build environment (a Yoshi flow runtime, a generated service client, an
+ * internal sibling) and are NOT needed to use the component. Substitute
+ * your own:
+ *   @wix/ambassador-cairo-dummyservice-v1-dummy-entity/types
+ */
 import React from 'react';
 import { CustomFieldsWidget } from '@wix/patterns';
 import { Button, Cell, Layout, Loader, Page } from '@wix/design-system';

package/dist/{docs → examples}/CustomFieldsWidget/responsive.tsx

@@ -1,3 +1,15 @@
+/**
+ * Illustrative example for `CustomFieldsWidget` — see `dist/docs/CustomFieldsWidget.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ *
+ * These imports are environment-scoped — they resolve only against a Wix
+ * build environment (a Yoshi flow runtime, a generated service client, an
+ * internal sibling) and are NOT needed to use the component. Substitute
+ * your own:
+ *   @wix/ambassador-cairo-dummyservice-v1-dummy-entity/types
+ */
 /* eslint-disable import/no-extraneous-dependencies */
 
 import React from 'react';

package/dist/{docs → examples}/CustomFieldsWidget/with-tpa-fields.tsx

@@ -1,3 +1,15 @@
+/**
+ * Illustrative example for `CustomFieldsWidget` — see `dist/docs/CustomFieldsWidget.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ *
+ * These imports are environment-scoped — they resolve only against a Wix
+ * build environment (a Yoshi flow runtime, a generated service client, an
+ * internal sibling) and are NOT needed to use the component. Substitute
+ * your own:
+ *   @wix/ambassador-cairo-dummyservice-v1-dummy-entity/types
+ */
 import React from 'react';
 import { CustomFieldsWidget } from '@wix/patterns';
 import { Button, Cell, Layout, Loader, Page } from '@wix/design-system';

package/dist/{docs → examples}/CustomFieldsWidget/without-entity-page.tsx

@@ -1,3 +1,15 @@
+/**
+ * Illustrative example for `CustomFieldsWidget` — see `dist/docs/CustomFieldsWidget.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ *
+ * These imports are environment-scoped — they resolve only against a Wix
+ * build environment (a Yoshi flow runtime, a generated service client, an
+ * internal sibling) and are NOT needed to use the component. Substitute
+ * your own:
+ *   @wix/ambassador-cairo-dummyservice-v1-dummy-entity/types
+ */
 import React from 'react';
 import {
   CustomFieldsWidget,

package/dist/{docs → examples}/EntityPage/2-columns.tsx

@@ -1,3 +1,9 @@
+/**
+ * Illustrative example for `EntityPage` — see `dist/docs/EntityPage.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ */
 import React from 'react';
 import {
   EntityPage,

package/dist/{docs → examples}/EntityPage/basic.tsx

@@ -1,3 +1,9 @@
+/**
+ * Illustrative example for `EntityPage` — see `dist/docs/EntityPage.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ */
 import React from 'react';
 import {
   EntityPage,

package/dist/{docs → examples}/EntityPage/delete-action.tsx

@@ -1,3 +1,9 @@
+/**
+ * Illustrative example for `EntityPage` — see `dist/docs/EntityPage.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ */
 import React from 'react';
 import {
   EntityPage,

package/dist/{docs → examples}/EntityPage/delete-error-handling.tsx

@@ -1,3 +1,9 @@
+/**
+ * Illustrative example for `EntityPage` — see `dist/docs/EntityPage.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ */
 import React from 'react';
 import {
   EntityPage,

package/dist/{docs → examples}/EntityPage/demo.tsx

@@ -1,3 +1,9 @@
+/**
+ * Illustrative example for `EntityPage` — see `dist/docs/EntityPage.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ */
 import React from 'react';
 import {
   CustomFieldsWidget,

package/dist/{docs → examples}/EntityPage/error-on-fetch.tsx

@@ -1,3 +1,9 @@
+/**
+ * Illustrative example for `EntityPage` — see `dist/docs/EntityPage.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ */
 import React from 'react';
 import {
   EntityPage,

package/dist/{docs → examples}/EntityPage/error-on-save.tsx

@@ -1,3 +1,9 @@
+/**
+ * Illustrative example for `EntityPage` — see `dist/docs/EntityPage.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ */
 import React from 'react';
 import {
   EntityPage,

package/dist/{docs → examples}/EntityPage/input-initialization-with-controller.tsx

@@ -1,3 +1,9 @@
+/**
+ * Illustrative example for `EntityPage` — see `dist/docs/EntityPage.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ */
 import React from 'react';
 import {
   EntityPage,

package/dist/{docs → examples}/EntityPage/input-initialization-with-usecontroller.tsx

@@ -1,3 +1,9 @@
+/**
+ * Illustrative example for `EntityPage` — see `dist/docs/EntityPage.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ */
 import React from 'react';
 import {
   EntityPage,

package/dist/{docs → examples}/EntityPage/loading.tsx

@@ -1,3 +1,9 @@
+/**
+ * Illustrative example for `EntityPage` — see `dist/docs/EntityPage.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ */
 import React from 'react';
 import { EntityPage, EntityPageState, useEntityPage } from '@wix/patterns';
 import { useForm } from '@wix/patterns/form';

package/dist/{docs → examples}/EntityPage/overriding-save-button-text.tsx

@@ -1,3 +1,9 @@
+/**
+ * Illustrative example for `EntityPage` — see `dist/docs/EntityPage.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ */
 import React from 'react';
 import {
   EntityPage,

package/dist/{docs → examples}/ExportTo/cta-is-out-of-the-table.tsx

@@ -1,3 +1,17 @@
+/**
+ * Illustrative example for `ExportTo` — see `dist/docs/ExportTo.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ *
+ * These imports are environment-scoped — they resolve only against a Wix
+ * build environment (a Yoshi flow runtime, a generated service client, an
+ * internal sibling) and are NOT needed to use the component. Substitute
+ * your own:
+ *   @wix/ambassador-contacts-v4-contact/http
+ *   @wix/ambassador-contacts-v4-contact/types
+ *   @wix/yoshi-flow-bm
+ */
 import { Avatar, Page, Button } from '@wix/design-system';
 import React from 'react';
 import {

package/dist/{docs → examples}/ExportTo/export-all-table.tsx

@@ -1,3 +1,17 @@
+/**
+ * Illustrative example for `ExportTo` — see `dist/docs/ExportTo.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ *
+ * These imports are environment-scoped — they resolve only against a Wix
+ * build environment (a Yoshi flow runtime, a generated service client, an
+ * internal sibling) and are NOT needed to use the component. Substitute
+ * your own:
+ *   @wix/ambassador-contacts-v4-contact/http
+ *   @wix/ambassador-contacts-v4-contact/types
+ *   @wix/yoshi-flow-bm
+ */
 import { Avatar, Page } from '@wix/design-system';
 import React from 'react';
 import {

package/dist/{docs → examples}/ExportTo/export-filtered-table.tsx

@@ -1,3 +1,17 @@
+/**
+ * Illustrative example for `ExportTo` — see `dist/docs/ExportTo.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ *
+ * These imports are environment-scoped — they resolve only against a Wix
+ * build environment (a Yoshi flow runtime, a generated service client, an
+ * internal sibling) and are NOT needed to use the component. Substitute
+ * your own:
+ *   @wix/ambassador-contacts-v4-contact/http
+ *   @wix/ambassador-contacts-v4-contact/types
+ *   @wix/yoshi-flow-bm
+ */
 import { Avatar, Page } from '@wix/design-system';
 import React from 'react';
 import {

package/dist/{docs → examples}/ExportTo/export-table-with-selection-bulk-selection.tsx

@@ -1,3 +1,17 @@
+/**
+ * Illustrative example for `ExportTo` — see `dist/docs/ExportTo.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ *
+ * These imports are environment-scoped — they resolve only against a Wix
+ * build environment (a Yoshi flow runtime, a generated service client, an
+ * internal sibling) and are NOT needed to use the component. Substitute
+ * your own:
+ *   @wix/ambassador-contacts-v4-contact/http
+ *   @wix/ambassador-contacts-v4-contact/types
+ *   @wix/yoshi-flow-bm
+ */
 import {
   Avatar,
   Card,

package/dist/{docs → examples}/Filter Overview/interactive-example.tsx

@@ -1,3 +1,9 @@
+/**
+ * Illustrative example for `Filter Overview` — see `dist/docs/Filter Overview.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ */
 import { Avatar, Badge } from '@wix/design-system';
 import React from 'react';
 /* eslint-disable import/no-extraneous-dependencies */

package/dist/{docs → examples}/Grid/card-with-a-cta-that-opens-a-modal.tsx

@@ -1,3 +1,9 @@
+/**
+ * Illustrative example for `Grid` — see `dist/docs/Grid.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ */
 import React from 'react';
 import { CollectionPage } from '@wix/patterns/page';
 import { Grid, useGridCollection, OffsetQuery } from '@wix/patterns';

package/dist/{docs → examples}/Grid/card-with-a-cta-that-opens-a-popup.tsx

@@ -1,3 +1,9 @@
+/**
+ * Illustrative example for `Grid` — see `dist/docs/Grid.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ */
 import React from 'react';
 import { AddItem, Box, Layout, Popover, TextButton } from '@wix/design-system';
 import { CollectionPage } from '@wix/patterns/page';

package/dist/{docs → examples}/Grid/demo.tsx

@@ -1,3 +1,9 @@
+/**
+ * Illustrative example for `Grid` — see `dist/docs/Grid.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ */
 import React from 'react';
 import { CollectionPage } from '@wix/patterns/page';
 import {

package/dist/{docs → examples}/Grid/grid-sections.tsx

@@ -1,3 +1,9 @@
+/**
+ * Illustrative example for `Grid` — see `dist/docs/Grid.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ */
 import React from 'react';
 import { CollectionPage } from '@wix/patterns/page';
 import {

package/dist/{docs → examples}/Grid/grid-with-a-reduced-width.tsx

@@ -1,3 +1,9 @@
+/**
+ * Illustrative example for `Grid` — see `dist/docs/Grid.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ */
 import React from 'react';
 import { Box, Card, Cell, Layout, Page } from '@wix/design-system';
 import { CollectionPage } from '@wix/patterns/page';

package/dist/{docs → examples}/Grid/use-the-preset-prop.tsx

@@ -1,3 +1,9 @@
+/**
+ * Illustrative example for `Grid` — see `dist/docs/Grid.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ */
 import React from 'react';
 import { CollectionPage } from '@wix/patterns/page';
 import { Grid, useGridCollection, OffsetQuery } from '@wix/patterns';

package/dist/{docs → examples}/ImportButton/backup-error-handling.tsx

@@ -1,3 +1,17 @@
+/**
+ * Illustrative example for `ImportButton` — see `dist/docs/ImportButton.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ *
+ * These imports are environment-scoped — they resolve only against a Wix
+ * build environment (a Yoshi flow runtime, a generated service client, an
+ * internal sibling) and are NOT needed to use the component. Substitute
+ * your own:
+ *   @wix/ambassador-stores-catalog-v1-product/http
+ *   @wix/ambassador-stores-catalog-v1-product/types
+ *   @wix/yoshi-flow-bm
+ */
 import { Page } from '@wix/design-system';
 import React from 'react';
 import {

package/dist/{docs → examples}/ImportButton/cms-import.tsx

@@ -1,3 +1,15 @@
+/**
+ * Illustrative example for `ImportButton` — see `dist/docs/ImportButton.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ *
+ * These imports are environment-scoped — they resolve only against a Wix
+ * build environment (a Yoshi flow runtime, a generated service client, an
+ * internal sibling) and are NOT needed to use the component. Substitute
+ * your own:
+ *   @wix/patterns-cms
+ */
 import React from 'react';
 import { CollectionPage } from '@wix/patterns/page';
 import { CustomColumns, ImportButton, Table } from '@wix/patterns';

package/dist/{docs → examples}/ImportButton/create-new-field.tsx

@@ -1,3 +1,15 @@
+/**
+ * Illustrative example for `ImportButton` — see `dist/docs/ImportButton.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ *
+ * These imports are environment-scoped — they resolve only against a Wix
+ * build environment (a Yoshi flow runtime, a generated service client, an
+ * internal sibling) and are NOT needed to use the component. Substitute
+ * your own:
+ *   @wix/patterns-cms
+ */
 import React from 'react';
 import { CollectionPage } from '@wix/patterns/page';
 import { CustomColumns, ImportButton, Table } from '@wix/patterns';

package/dist/{docs → examples}/ImportButton/platformized-import-fields-inline.tsx

@@ -1,3 +1,17 @@
+/**
+ * Illustrative example for `ImportButton` — see `dist/docs/ImportButton.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ *
+ * These imports are environment-scoped — they resolve only against a Wix
+ * build environment (a Yoshi flow runtime, a generated service client, an
+ * internal sibling) and are NOT needed to use the component. Substitute
+ * your own:
+ *   @wix/ambassador-stores-catalog-v1-product/http
+ *   @wix/ambassador-stores-catalog-v1-product/types
+ *   @wix/yoshi-flow-bm
+ */
 import { Page } from '@wix/design-system';
 import React from 'react';
 import {

package/dist/{docs → examples}/ImportButton/platformized-import-from-a-source.tsx

@@ -1,3 +1,9 @@
+/**
+ * Illustrative example for `ImportButton` — see `dist/docs/ImportButton.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ */
 import React from 'react';
 import { CollectionPage } from '@wix/patterns/page';
 import { CustomColumns, ImportButton, Table } from '@wix/patterns';

package/dist/{docs → examples}/ImportButton/required-fields.tsx

@@ -1,3 +1,17 @@
+/**
+ * Illustrative example for `ImportButton` — see `dist/docs/ImportButton.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ *
+ * These imports are environment-scoped — they resolve only against a Wix
+ * build environment (a Yoshi flow runtime, a generated service client, an
+ * internal sibling) and are NOT needed to use the component. Substitute
+ * your own:
+ *   @wix/ambassador-stores-catalog-v1-product/http
+ *   @wix/ambassador-stores-catalog-v1-product/types
+ *   @wix/yoshi-flow-bm
+ */
 import { Page } from '@wix/design-system';
 import React from 'react';
 import {

package/dist/{docs → examples}/ImportButton/update-or-skip-by-id.tsx

@@ -1,3 +1,15 @@
+/**
+ * Illustrative example for `ImportButton` — see `dist/docs/ImportButton.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ *
+ * These imports are environment-scoped — they resolve only against a Wix
+ * build environment (a Yoshi flow runtime, a generated service client, an
+ * internal sibling) and are NOT needed to use the component. Substitute
+ * your own:
+ *   @wix/patterns-cms
+ */
 import React from 'react';
 import { CollectionPage } from '@wix/patterns/page';
 import { CustomColumns, ImportButton, Table } from '@wix/patterns';

package/dist/{docs → examples}/Indeterminate/all-indeterminate.tsx

@@ -1,3 +1,17 @@
+/**
+ * Illustrative example for `Indeterminate` — see `dist/docs/Indeterminate.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ *
+ * These imports are environment-scoped — they resolve only against a Wix
+ * build environment (a Yoshi flow runtime, a generated service client, an
+ * internal sibling) and are NOT needed to use the component. Substitute
+ * your own:
+ *   @wix/ambassador-contacts-v4-contact/http
+ *   @wix/ambassador-contacts-v4-contact/types
+ *   @wix/fe-essentials/react
+ */
 import { Avatar, EmptyState, Page } from '@wix/design-system';
 import React from 'react';
 import { queryContacts } from '@wix/ambassador-contacts-v4-contact/http';

package/dist/{docs → examples}/Indeterminate/items-indeterminate-status.tsx

@@ -1,3 +1,17 @@
+/**
+ * Illustrative example for `Indeterminate` — see `dist/docs/Indeterminate.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ *
+ * These imports are environment-scoped — they resolve only against a Wix
+ * build environment (a Yoshi flow runtime, a generated service client, an
+ * internal sibling) and are NOT needed to use the component. Substitute
+ * your own:
+ *   @wix/ambassador-contacts-v4-contact/http
+ *   @wix/ambassador-contacts-v4-contact/types
+ *   @wix/fe-essentials/react
+ */
 import { Avatar, EmptyState, Page } from '@wix/design-system';
 import React from 'react';
 import { queryContacts } from '@wix/ambassador-contacts-v4-contact/http';

package/dist/{docs → examples}/Internal Scroll/full-width-section.tsx

@@ -1,3 +1,9 @@
+/**
+ * Illustrative example for `Internal Scroll` — see `dist/docs/Internal Scroll.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ */
 import { Avatar, Box, Card } from '@wix/design-system';
 import React from 'react';
 import { CollectionPage } from '@wix/patterns/page';

package/dist/{docs → examples}/Internal Scroll/narrow-side-section.tsx

@@ -1,3 +1,9 @@
+/**
+ * Illustrative example for `Internal Scroll` — see `dist/docs/Internal Scroll.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ */
 import { Avatar, Box, Card } from '@wix/design-system';
 import React from 'react';
 import { CollectionPage } from '@wix/patterns/page';

package/dist/{docs → examples}/More Actions/collection-page-2.tsx

@@ -1,3 +1,9 @@
+/**
+ * Illustrative example for `More Actions` — see `dist/docs/More Actions.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ */
 import { Avatar } from '@wix/design-system';
 import React from 'react';
 import {

package/dist/{docs → examples}/More Actions/collection-page.tsx

@@ -1,3 +1,9 @@
+/**
+ * Illustrative example for `More Actions` — see `dist/docs/More Actions.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ */
 import { Avatar } from '@wix/design-system';
 import React from 'react';
 import {

package/dist/{docs → examples}/More Actions/explore-related-apps.tsx

@@ -1,3 +1,9 @@
+/**
+ * Illustrative example for `More Actions` — see `dist/docs/More Actions.md`.
+ *
+ * It demonstrates one API; the data source, http client and layout around
+ * that are scaffolding to make the snippet runnable, not requirements.
+ */
 import { Avatar, CustomModalLayout, Modal } from '@wix/design-system';
 import React from 'react';
 import {