@wordpress/components 16.0.1-next.5df0cd52b7.0 → 19.0.1

package/CHANGELOG.md

@@ -2,19 +2,86 @@
 
 ## Unreleased
 
-## 16.0.0-next.0 (2021-08-17)
+## 19.0.1 (2021-11-07)
+
+### Experimental
+
+-   Updated the `ToolsPanel` to use `Grid` internally to manage panel layout ([35621](https://github.com/WordPress/gutenberg/pull/35621)).
+
+## 19.0.0 (2021-10-22)
+
+### New Features
+
+-   Added support for `step="any"` in `NumberControl` and `RangeControl` ([#34542](https://github.com/WordPress/gutenberg/pull/34542)).
+
+### Enhancements
+
+-   Removed the separator shown between `ToggleGroupControl` items ([#35497](https://github.com/WordPress/gutenberg/pull/35497)).
+-   The `ColorPicker` component property `onChangeComplete`, a function accepting a color object, was replaced with the property `onChange`, a function accepting a  string on  ([#35220](https://github.com/WordPress/gutenberg/pull/35220)).
+-   The property `disableAlpha`, was removed from the `ColorPicker` component. Use the new opposite property `enableAlpha` instead ([#35220](https://github.com/WordPress/gutenberg/pull/35220)).
+
+### Experimental
+
+-   Removed the `fieldset` wrapper from the `FontAppearanceControl` component ([35461](https://github.com/WordPress/gutenberg/pull/35461)).
+-   Refactored the `ToggleGroupControl` component's structure and embedded `ToggleGroupControlButton` directly into `ToggleGroupControlOption` ([#35600](https://github.com/WordPress/gutenberg/pull/35600)).
+-   Added support for showing an experimental hint in `CustomSelectControl`  ([#35673](https://github.com/WordPress/gutenberg/pull/35673)).
+
+### Breaking Changes
+
+-   The `color` property a `tinycolor2` color object passed on `onChangeComplete` property of the `ColorPicker` component was removed. Please use the new `onChange` property that accepts a string color representation ([#35562](https://github.com/WordPress/gutenberg/pull/35562)).
+
+## 18.0.0 (2021-10-12)
+
+### Breaking Changes
+
+-   Removed the deprecated `position` and `menuLabel` from the `DropdownMenu` component ([#34537](https://github.com/WordPress/gutenberg/pull/34537)).
+-   Removed the deprecated `onClickOutside` prop from the `Popover` component ([#34537](https://github.com/WordPress/gutenberg/pull/34537)).
+-   Changed `RangeControl` component to not apply `shiftStep` to inputs from its `<input type="range"/>` ([35020](https://github.com/WordPress/gutenberg/pull/35020)).
+-   Removed `isAction` prop from `Item`. The component will now rely on `onClick` to render as a `button` ([35152](https://github.com/WordPress/gutenberg/pull/35152)).
+
+### New Features
+
+-   Add an experimental `Navigator` components ([#34904](https://github.com/WordPress/gutenberg/pull/34904)) as a replacement for the previous `Navigation` related components.
+-   Update the `ColorPicker` component to the latest design ([#35220](https://github.com/WordPress/gutenberg/pull/35220))
 
 ### Bug Fix
 
--   Listen to `resize` events correctly in `useBreakpointIndex`. This hook is used in `useResponsiveValue` and consequently in the `Flex` and `Grid` components  ([#33902](https://github.com/WordPress/gutenberg/pull/33902))
+-   Fixed rounding of value in `RangeControl` component when it loses focus while the `SHIFT` key is held. ([#35020](https://github.com/WordPress/gutenberg/pull/35020)).
+
+### Internal
+
+-   Deleted the `createComponent` utility function ([#34929](https://github.com/WordPress/gutenberg/pull/34929)).
+-   Deleted the `useJumpStep` utility function ([#35561](https://github.com/WordPress/gutenberg/pull/35561)).
+
+## 17.0.0 (2021-09-09)
 
 ### Breaking Change
 
--	Updated the visual styles of the RangeControl component ([#33824](https://github.com/WordPress/gutenberg/pull/33824))
+-   Removed a min-width from the `DropdownMenu` component, allowing the menu to accommodate thin contents like vertical tools menus ([#33995](https://github.com/WordPress/gutenberg/pull/33995)).
+
+### Bug Fix
+
+-   Fixed RTL styles in `Flex` component ([#33729](https://github.com/WordPress/gutenberg/pull/33729)).
+-   Fixed unit test errors caused by `CSS.supports` being called in a non-browser environment ([#34572](https://github.com/WordPress/gutenberg/pull/34572)).
+-   Fixed `ToggleGroupControl`'s backdrop not updating when changing the `isAdaptiveWidth` property ([#34595](https://github.com/WordPress/gutenberg/pull/34595)).
+
+### Internal
+
+-   Renamed `PolymorphicComponent*` types to `WordPressComponent*` ([#34330](https://github.com/WordPress/gutenberg/pull/34330)).
+
+## 16.0.0 (2021-08-23)
+
+### Breaking Change
+
+-   Updated the visual styles of the RangeControl component ([#33824](https://github.com/WordPress/gutenberg/pull/33824)).
 
 ### New Feature
 
--	Add `hideLabelFromVision` prop to `RangeControl` ([#33714](https://github.com/WordPress/gutenberg/pull/33714))
+-   Add `hideLabelFromVision` prop to `RangeControl` ([#33714](https://github.com/WordPress/gutenberg/pull/33714)).
+
+### Bug Fix
+
+-   Listen to `resize` events correctly in `useBreakpointIndex`. This hook is used in `useResponsiveValue` and consequently in the `Flex` and `Grid` components ([#33902](https://github.com/WordPress/gutenberg/pull/33902))
 
 ## 15.0.0 (2021-07-29)
 

package/CONTRIBUTING.md

@@ -4,12 +4,404 @@ Thank you for taking the time to contribute.
 
 The following is a set of guidelines for contributing to the `@wordpress/components` package to be considered in addition to the general ones described in our [Contributing Policy](/CONTRIBUTING.md).
 
-## Examples
+This set of guidelines should apply especially to newly introduced components. In fact, while these guidelines should also be retroactively applied to existing components, it is sometimes impossible to do so for legacy/compatibility reasons.
 
-Each component needs to include an example in its README.md file to demonstrate the usage of the component.
+For an example of a component that follows these requirements, take a look at [`ItemGroup`](/packages/components/src/item-group).
 
-These examples can be consumed automatically from other projects in order to visualize them in their documentation. To ensure these examples are extractable, compilable and renderable, they should be structured in the following way:
+- [Compatibility](#compatibility)
+- [Compound components](#compound-components)
+- [Components & Hooks](#components--hooks)
+- [TypeScript](#typescript)
+- [Styling](#styling)
+- [Context system](#context-system)
+- [Unit tests](#unit-tests)
+- [Storybook](#storybook)
+- [Documentation](#documentation)
+- [README example](#README-example)
+- [Folder structure](#folder-structure)
 
--   It has to be included in a `jsx` code block.
--   It has to work out-of-the-box. No additional code should be needed to have working the example.
--   It has to define a React component called `My<ComponentName>` which renders the example (i.e.: `MyButton`). Examples for the Higher Order Components should define a `MyComponent<ComponentName>` component (i.e.: `MyComponentWithNotices`).
+## Compatibility
+
+The `@wordpress/components` package includes components that are relied upon by many developers across different projects. It is, therefore, very important to avoid introducing breaking changes.
+
+In these situations, one possible approach is to "soft-deprecate" a given legacy API. This is achieved by:
+
+1. Removing traces of the API from the docs, while still supporting it in code.
+2. Updating all places in Gutenberg that use that API.
+3. Adding deprecation warnings (only after the previous point is completed, otherwise the Browser Console will be polluted by all those warnings and some e2e tests may fail).
+
+When adding new components or new props to existing components, it's recommended to prefix them with `__unstable` or `__experimental` until they're stable enough to be exposed as part of the public API.
+
+Learn more on [How to preserve backward compatibility for a React Component](/docs/how-to-guides/backward-compatibility/README.md#how-to-preserve-backward-compatibility-for-a-react-component) and [Experimental and Unstable APIs](/docs/contributors/code/coding-guidelines.md#experimental-and-unstable-apis).
+
+<!-- ## Polymorphic Components (i.e. the `as` prop)
+
+The primary way to compose components is through the `as` prop. This prop can be used to change the underlying element used to render a component, e.g.:
+
+```tsx
+function LinkButton( { href, children } ) {
+	return <Button variant="primary" as="a" href={href}>{ children }</Button>;
+}
+```
+-->
+
+## Compound components
+
+When creating components that render a list of subcomponents, prefer to expose the API using the [Compound Components](https://kentcdodds.com/blog/compound-components-with-react-hooks) technique over array props like `items` or `options`:
+
+```jsx
+// ❌ Don't:
+<List
+	items={ [
+		{ value: 'Item 1' },
+		{ value: 'Item 2' },
+		{ value: 'Item 3' },
+	] }
+/>
+```
+
+```jsx
+// ✅ Do:
+<List>
+	<ListItem value="Item 1" />
+	<ListItem value="Item 2" />
+	<ListItem value="Item 3" />
+</List>
+```
+
+When implementing this pattern, avoid using `React.Children.map` and `React.cloneElement` to map through the children and augment them. Instead, use React Context to provide state to subcomponents and connect them:
+
+```jsx
+// ❌ Don't:
+function List ( props ) {
+	const [ state, setState ] = useState();
+	return (
+		<div { ...props }>
+			{ Children.map( props.children, ( child ) => cloneElement( child, { state } ) ) ) }
+		</div>
+	);
+}
+```
+
+```jsx
+// ✅ Do:
+const ListContext = createContext();
+
+function List( props ) {
+	const [ state, setState ] = useState();
+	return (
+		<ListContext.Provider value={ state }>
+			<div { ...props } />
+		</ListContext.Provider>
+	);
+}
+
+function ListItem( props ) {
+	const state = useContext( ListContext );
+	...
+}
+```
+
+<!-- ## (Semi-)Controlled components
+
+TBD
+
+## Layout "responsibilities"
+
+TBD — Components' layout responsibilities and boundaries (i.e., a component should only affect the layout of its children, not its own) -->
+
+## Components & Hooks
+
+One way to enable reusability and composition is to extract a component's underlying logic into a hook (living in a separate `hook.ts` file). The actual component (usually defined in a `component.tsx` file) can then invoke the hook and use its output to render the required DOM elements. For example:
+
+```tsx
+// in `hook.ts`
+function useExampleComponent( props: PolymorphicComponentProps< ExampleProps, 'div' > ) {
+	// Merge received props with the context system.
+	const { isVisible, className, ...otherProps } = useContextSystem( props, 'Example' );
+
+	// Any other reusable rendering logic (e.g. computing className, state, event listeners...)
+	const cx = useCx();
+	const classes = useMemo(
+		() =>
+			cx(
+				styles.example,
+				isVisible && styles.visible,
+				className
+			),
+		[ className, isVisible ]
+	);
+
+	return {
+		...otherProps,
+		className: classes
+	};
+}
+
+// in `component.tsx`
+function Example(
+	props: PolymorphicComponentProps< ExampleProps, 'div' >,
+	forwardedRef: Ref< any >
+) {
+	const exampleProps = useExampleComponent( props );
+
+	return <View { ...spacerProps } ref={ forwardedRef } />;
+}
+```
+
+A couple of good examples of how hooks are used for composition are:
+
+- the `Card` component, which builds on top of the `Surface` component by [calling the `useSurface` hook inside its own hook](/packages/components/src/card/card/hook.js);
+- the `HStack` component, which builds on top of the `Flex` component and [calls the `useFlex` hook inside its own hook](/packages/components/src/h-stack/hook.js).
+
+<!-- ## API Consinstency
+
+[To be expanded] E.g.:
+
+- Boolean component props should be prefixed with `is*` (e.g. `isChecked`), `has*` (e.g. `hasValue`) or `enable*` (e.g. `enableScroll`)
+- Event callback props should be prefixed with `on*` (e.g. `onChanged`)
+- Subcomponents naming conventions (e.g `CardBody` instead of `Card.Body`)
+- ...
+
+## Performance
+
+TDB -->
+
+## TypeScript
+
+We strongly encourage using TypeScript for all new components. Components should be typed using the `WordPressComponent` type.
+
+<!-- TODO: add to the previous paragraph once the composision section gets added to this document.
+(more details about polymorphism can be found above in the "Components composition" section). -->
+
+## Styling
+
+All new component should be styled using [Emotion](https://emotion.sh/docs/introduction).
+
+Note: Instead of using Emotion's standard `cx` function, the custom [`useCx` hook](/packages/components/src/utils/hooks/use-cx.ts) should be used instead.
+
+## Context system
+
+The `@wordpress/components` context system is based on [React's `Context` API](https://reactjs.org/docs/context.html), and is a way for components to adapt to the "context" they're being rendered in.
+
+Components can use this system via a couple of functions:
+
+- they can provide values using a shared `ContextSystemProvider` component
+- they can connect to the Context via `contextConnect`
+- they can read the "computed" values from the context via `useContextSystem`
+
+An example of how this is used can be found in the [`Card` component family](/packages/components/src/card). For example, this is how the `Card` component injects the `size` and `isBorderless` props down to its `CardBody` subcomponent — which makes it use the correct spacing and border settings "auto-magically".
+
+```jsx
+//=========================================================================
+// Simplified snippet from `packages/components/src/card/card/hook.js`
+//=========================================================================
+import { useContextSystem } from '../../ui/context';
+
+export function useCard( props ) {
+	// Read any derived registered prop from the Context System in the `Card` namespace
+	const derivedProps = useContextSystem( props, 'Card' );
+
+	// [...]
+
+	return computedHookProps;
+}
+
+//=========================================================================
+// Simplified snippet from `packages/components/src/card/card/component.js`
+//=========================================================================
+import { contextConnect, ContextSystemProvider } from '../../ui/context';
+
+function Card( props, forwardedRef ) {
+	const {
+		size,
+		isBorderless,
+		...otherComputedHookProps
+	} = useCard( props );
+
+	// [...]
+
+	// Prepare the additional props that should be passed to subcomponents via the Context System.
+	const contextProviderValue = useMemo( () => {
+		return {
+			// Each key in this object should match a component's registered namespace.
+			CardBody: {
+				size,
+				isBorderless,
+			},
+		};
+	}, [ isBorderless, size ] );
+
+	return (
+		{ /* Write additional values to the Context System */ }
+		<ContextSystemProvider value={ contextProviderValue }>
+			{ /* [...] */ }
+		</ContextSystemProvider>
+	);
+}
+
+// Connect to the Context System under the `Card` namespace
+const ConnectedCard = contextConnect( Card, 'Card' );
+export default ConnectedCard;
+
+//=========================================================================
+// Simplified snippet from `packages/components/src/card/card-body/hook.js`
+//=========================================================================
+import { useContextSystem } from '../../ui/context';
+
+export function useCardBody( props ) {
+	// Read any derived registered prop from the Context System in the `CardBody` namespace.
+	// If a `CardBody` component is rendered as a child of a `Card` component, the value of
+	// the `size` prop will be the one set by the parent `Card` component via the Context
+	// System (unless the prop gets explicitely set on the `CardBody` component).
+	const { size = 'medium', ...otherDerivedProps } = useContextSystem( props, 'CardBody' );
+
+	// [...]
+
+	return computedHookProps;
+}
+```
+
+## Unit tests
+
+Please refer to the [JavaScript Testing Overview docs](/docs/contributors/code/testing-overview.md#snapshot-testing).
+
+## Storybook
+
+All new components should add stories to the project's [Storybook](https://storybook.js.org/). Each [story](https://storybook.js.org/docs/react/get-started/whats-a-story) captures the rendered state of a UI component in isolation. This greatly simplifies working on a given component, while also serving as an interactive form of documentation.
+
+A component's story should be showcasing its different states — for example, the different variants of a  `Button`:
+
+```jsx
+import Button from '../';
+
+export default { title: 'Components/Button', component: Button };
+
+const Template = ( args ) => <Button { ...args } />;
+
+export const Default = Template.bind( {} );
+Default.args = {
+	text: 'Default Button',
+	isBusy: false,
+	isSmall: false,
+};
+
+export const Primary = Template.bind( {} );
+Primary.args = {
+	...Default.args,
+	text: 'Primary Button',
+	variant: 'primary',
+};
+```
+
+A great tool to use when writing stories is the [Storybook Controls addon](https://storybook.js.org/addons/@storybook/addon-controls). Ideally props should be exposed by using this addon, which provides a graphical UI to interact dynamically with the component without needing to write code. Avoid using [Knobs](https://storybook.js.org/addons/@storybook/addon-knobs) for new stories, as this addon is deprecated.
+
+The default value of each control should coincide with the default value of the props (i.e. it should be `undefined` if a prop is not required). A story should, therefore, also explicitly show how values from the Context System are applied to (sub)components. A good example of how this may look like is the [`Card` story](https://wordpress.github.io/gutenberg/?path=/story/components-card--default) (code [here](/packages/components/src/card/stories/index.js)).
+
+Storybook can be started on a local machine by running `npm run storybook:dev`. Alternatively, the components' catalogue (up to date with the latest code on `trunk`) can be found at [wordpress.github.io/gutenberg/](https://wordpress.github.io/gutenberg/).
+
+## Documentation
+
+All components, in addition to being typed, should be using JSDoc when necessary — as explained in the [Coding Guidelines](/docs/contributors/code/coding-guidelines.md#javascript-documentation-using-jsdoc).
+
+Each component that is exported from the `@wordpress/components` package should include a `README.md` file, explaining how to use the component, showing examples, and documenting all the props.
+
+## README example
+
+````markdown
+# `ComponentName`
+
+<!-- If component is experimental, add the following section: -->
+<div class="callout callout-alert">
+This feature is still experimental. “Experimental” means this is an early implementation subject to drastic and breaking changes.
+</div>
+
+<!-- If component is deprecated, add the following section: -->
+<div class="callout callout-alert">
+This component is deprecated. Please use `{other component}` from the `{other package}` package instead.
+</div>
+
+Description of the component.
+
+## Usage
+
+Code example using correct markdown syntax and formatted using project's formatting rules. See [ItemGroup](/packages/components/src/item-group/item-group/README.md#usage) for a real-world example.
+
+```jsx
+import { ExampleComponent } from '@wordpress/components';
+
+function Example() {
+	return (
+		<ExampleComponent>
+			<p>Code is poetry</p>
+		</ExampleComponent>
+	);
+}
+```
+
+## Props
+
+The component accepts the following props:
+
+### `propName`: Typescript style type i.e `string`, `number`, `( nextValue: string ) => void`
+
+Prop description. With a new line before and after the description and before and after type/required blocks.
+
+-   Required: Either `Yes` or `No`
+<!-- If the prop has a default value, add the following line: -->
+-   Default: [default value]
+
+### Inherited props
+
+Add this section when there are props that are drilled down into an internal component. See [ClipboardButton](/packages/components/src/clipboard-button/README.md) for an example.
+
+<!-- Only add the next section if the component relies on the [Context System](#context-system) -->
+## Context
+
+See examples for this section for the [ItemGroup](/packages/components/src/item-group/item-group/README.md#context) and [`Card`](/packages/components/src/card/card/README.md#context) components.
+````
+
+## Folder structure
+
+As a result of the above guidelines, all new components (except for shared utilities) should _generally_ follow this folder structure:
+
+```text
+component-name/
+├── stories
+│   └── index.js
+├── test
+│   └── index.js
+├── component.tsx
+├── context.ts
+├── hook.ts
+├── index.ts
+├── README.md
+├── styles.ts
+└── types.ts
+```
+
+In case of a family of components (e.g. `Card` and `CardBody`, `CardFooter`, `CardHeader` ...), each component's implementation should live in a separate subfolder, while code common to the whole family of components (e.g types, utils, context...) should live in the family of components root folder:
+
+```text
+component-family-name/
+├── sub-component-name/
+│   ├── index.ts
+│   ├── component.tsx
+│   ├── hook.ts
+│   ├── README.md
+│   └── styles.ts
+├── sub-component-name/
+│   ├── index.ts
+│   ├── component.tsx
+│   ├── hook.ts
+│   ├── README.md
+│   └── styles.ts
+├── stories
+│   └── index.js
+├── test
+│   └── index.js
+├── context.ts
+├── index.ts
+├── types.ts
+└── utils.ts
+```

package/README.md

@@ -10,7 +10,7 @@ Install the module
 npm install @wordpress/components --save
 ```
 
-_This package assumes that your code will run in an **ES2015+** environment. If you're using an environment that has limited or no support for ES2015+ such as IE browsers then using [core-js](https://github.com/zloirock/core-js) will add polyfills for these methods._
+_This package assumes that your code will run in an **ES2015+** environment. If you're using an environment that has limited or no support for such language features and APIs, you should include [the polyfill shipped in `@wordpress/babel-preset-default`](https://github.com/WordPress/gutenberg/tree/HEAD/packages/babel-preset-default#polyfill) in your code._
 
 ## Usage
 
@@ -32,3 +32,11 @@ Many components include CSS to add style, you will need to add in order to appea
 In non-WordPress projects, link to the `build-style/style.css` file directly, it is located at `node_modules/@wordpress/components/build-style/style.css`.
 
 <br/><br/><p align="center"><img src="https://s.w.org/style/images/codeispoetry.png?1" alt="Code is Poetry." /></p>
+
+## Docs & examples
+
+You can browse the components docs and examples at https://wordpress.github.io/gutenberg/
+
+## Contributing
+
+See [CONTRIBUTING.md](/packages/components/CONTRIBUTING.md) for the contributing guidelines for the `@wordpress/components` package.

package/build/angle-picker-control/index.js

@@ -9,24 +9,24 @@ exports.default = AnglePickerControl;
 
 var _element = require("@wordpress/element");
 
-var _extends2 = _interopRequireDefault(require("@babel/runtime/helpers/extends"));
-
 var _classnames = _interopRequireDefault(require("classnames"));
 
-var _compose = require("@wordpress/compose");
-
 var _i18n = require("@wordpress/i18n");
 
-var _baseControl = _interopRequireDefault(require("../base-control"));
-
 var _flex = require("../flex");
 
-var _numberControl = _interopRequireDefault(require("../number-control"));
+var _inputControl = _interopRequireDefault(require("../input-control"));
 
 var _angleCircle = _interopRequireDefault(require("./angle-circle"));
 
 var _anglePickerControlStyles = require("./styles/angle-picker-control-styles");
 
+var _space = require("../ui/utils/space");
+
+var _text = require("../text");
+
+var _spacer = require("../spacer");
+
 /**
  * External dependencies
  */
@@ -40,39 +40,44 @@ var _anglePickerControlStyles = require("./styles/angle-picker-control-styles");
  */
 function AnglePickerControl({
   className,
-  hideLabelFromVision,
-  id: idProp,
   label = (0, _i18n.__)('Angle'),
   onChange,
-  value,
-  ...props
+  value
 }) {
-  const instanceId = (0, _compose.useInstanceId)(AnglePickerControl, 'components-angle-picker-control__input');
-  const id = idProp || instanceId;
-
   const handleOnNumberChange = unprocessedValue => {
     const inputValue = unprocessedValue !== '' ? parseInt(unprocessedValue, 10) : 0;
     onChange(inputValue);
   };
 
   const classes = (0, _classnames.default)('components-angle-picker-control', className);
-  return (0, _element.createElement)(_baseControl.default, (0, _extends2.default)({
-    className: classes,
-    hideLabelFromVision: hideLabelFromVision,
-    id: id,
-    label: label
-  }, props), (0, _element.createElement)(_anglePickerControlStyles.Root, null, (0, _element.createElement)(_flex.FlexBlock, null, (0, _element.createElement)(_numberControl.default, {
+  return (0, _element.createElement)(_anglePickerControlStyles.Root, {
+    className: classes
+  }, (0, _element.createElement)(_flex.FlexBlock, null, (0, _element.createElement)(_inputControl.default, {
+    label: label,
     className: "components-angle-picker-control__input-field",
-    id: id,
     max: 360,
     min: 0,
     onChange: handleOnNumberChange,
     step: "1",
-    value: value
-  })), (0, _element.createElement)(_flex.FlexItem, null, (0, _element.createElement)(_angleCircle.default, {
+    value: value,
+    hideHTMLArrows: true,
+    suffix: (0, _element.createElement)(_spacer.Spacer, {
+      as: _text.Text,
+      marginRight: (0, _space.space)(3),
+      style: {
+        color: 'var( --wp-admin-theme-color )'
+      }
+    }, "\xB0")
+  })), (0, _element.createElement)(_flex.FlexItem, {
+    style: {
+      marginLeft: (0, _space.space)(4),
+      marginBottom: (0, _space.space)(1),
+      marginTop: 'auto'
+    }
+  }, (0, _element.createElement)(_angleCircle.default, {
     "aria-hidden": "true",
     value: value,
     onChange: onChange
-  }))));
+  })));
 }
 //# sourceMappingURL=index.js.map

package/build/angle-picker-control/index.js.map

@@ -1 +1 @@
-{"version":3,"sources":["@wordpress/components/src/angle-picker-control/index.js"],"names":["AnglePickerControl","className","hideLabelFromVision","id","idProp","label","onChange","value","props","instanceId","handleOnNumberChange","unprocessedValue","inputValue","parseInt","classes"],"mappings":";;;;;;;;;;;;;AAGA;;AAKA;;AACA;;AAKA;;AACA;;AACA;;AACA;;AACA;;AAlBA;AACA;AACA;;AAGA;AACA;AACA;;AAIA;AACA;AACA;AAOe,SAASA,kBAAT,CAA6B;AAC3CC,EAAAA,SAD2C;AAE3CC,EAAAA,mBAF2C;AAG3CC,EAAAA,EAAE,EAAEC,MAHuC;AAI3CC,EAAAA,KAAK,GAAG,cAAI,OAAJ,CAJmC;AAK3CC,EAAAA,QAL2C;AAM3CC,EAAAA,KAN2C;AAO3C,KAAGC;AAPwC,CAA7B,EAQX;AACH,QAAMC,UAAU,GAAG,4BAClBT,kBADkB,EAElB,wCAFkB,CAAnB;AAIA,QAAMG,EAAE,GAAGC,MAAM,IAAIK,UAArB;;AAEA,QAAMC,oBAAoB,GAAKC,gBAAF,IAAwB;AACpD,UAAMC,UAAU,GACfD,gBAAgB,KAAK,EAArB,GAA0BE,QAAQ,CAAEF,gBAAF,EAAoB,EAApB,CAAlC,GAA6D,CAD9D;AAEAL,IAAAA,QAAQ,CAAEM,UAAF,CAAR;AACA,GAJD;;AAMA,QAAME,OAAO,GAAG,yBAAY,iCAAZ,EAA+Cb,SAA/C,CAAhB;AAEA,SACC,4BAAC,oBAAD;AACC,IAAA,SAAS,EAAGa,OADb;AAEC,IAAA,mBAAmB,EAAGZ,mBAFvB;AAGC,IAAA,EAAE,EAAGC,EAHN;AAIC,IAAA,KAAK,EAAGE;AAJT,KAKMG,KALN,GAOC,4BAAC,8BAAD,QACC,4BAAC,eAAD,QACC,4BAAC,sBAAD;AACC,IAAA,SAAS,EAAC,8CADX;AAEC,IAAA,EAAE,EAAGL,EAFN;AAGC,IAAA,GAAG,EAAG,GAHP;AAIC,IAAA,GAAG,EAAG,CAJP;AAKC,IAAA,QAAQ,EAAGO,oBALZ;AAMC,IAAA,IAAI,EAAC,GANN;AAOC,IAAA,KAAK,EAAGH;AAPT,IADD,CADD,EAYC,4BAAC,cAAD,QACC,4BAAC,oBAAD;AACC,mBAAY,MADb;AAEC,IAAA,KAAK,EAAGA,KAFT;AAGC,IAAA,QAAQ,EAAGD;AAHZ,IADD,CAZD,CAPD,CADD;AA8BA","sourcesContent":["/**\n * External dependencies\n */\nimport classnames from 'classnames';\n\n/**\n * WordPress dependencies\n */\nimport { useInstanceId } from '@wordpress/compose';\nimport { __ } from '@wordpress/i18n';\n\n/**\n * Internal dependencies\n */\nimport BaseControl from '../base-control';\nimport { FlexBlock, FlexItem } from '../flex';\nimport NumberControl from '../number-control';\nimport AngleCircle from './angle-circle';\nimport { Root } from './styles/angle-picker-control-styles';\n\nexport default function AnglePickerControl( {\n\tclassName,\n\thideLabelFromVision,\n\tid: idProp,\n\tlabel = __( 'Angle' ),\n\tonChange,\n\tvalue,\n\t...props\n} ) {\n\tconst instanceId = useInstanceId(\n\t\tAnglePickerControl,\n\t\t'components-angle-picker-control__input'\n\t);\n\tconst id = idProp || instanceId;\n\n\tconst handleOnNumberChange = ( unprocessedValue ) => {\n\t\tconst inputValue =\n\t\t\tunprocessedValue !== '' ? parseInt( unprocessedValue, 10 ) : 0;\n\t\tonChange( inputValue );\n\t};\n\n\tconst classes = classnames( 'components-angle-picker-control', className );\n\n\treturn (\n\t\t<BaseControl\n\t\t\tclassName={ classes }\n\t\t\thideLabelFromVision={ hideLabelFromVision }\n\t\t\tid={ id }\n\t\t\tlabel={ label }\n\t\t\t{ ...props }\n\t\t>\n\t\t\t<Root>\n\t\t\t\t<FlexBlock>\n\t\t\t\t\t<NumberControl\n\t\t\t\t\t\tclassName=\"components-angle-picker-control__input-field\"\n\t\t\t\t\t\tid={ id }\n\t\t\t\t\t\tmax={ 360 }\n\t\t\t\t\t\tmin={ 0 }\n\t\t\t\t\t\tonChange={ handleOnNumberChange }\n\t\t\t\t\t\tstep=\"1\"\n\t\t\t\t\t\tvalue={ value }\n\t\t\t\t\t/>\n\t\t\t\t</FlexBlock>\n\t\t\t\t<FlexItem>\n\t\t\t\t\t<AngleCircle\n\t\t\t\t\t\taria-hidden=\"true\"\n\t\t\t\t\t\tvalue={ value }\n\t\t\t\t\t\tonChange={ onChange }\n\t\t\t\t\t/>\n\t\t\t\t</FlexItem>\n\t\t\t</Root>\n\t\t</BaseControl>\n\t);\n}\n"]}
+{"version":3,"sources":["@wordpress/components/src/angle-picker-control/index.js"],"names":["AnglePickerControl","className","label","onChange","value","handleOnNumberChange","unprocessedValue","inputValue","parseInt","classes","Text","color","marginLeft","marginBottom","marginTop"],"mappings":";;;;;;;;;;;AAGA;;AAKA;;AAKA;;AACA;;AACA;;AACA;;AACA;;AACA;;AACA;;AAnBA;AACA;AACA;;AAGA;AACA;AACA;;AAGA;AACA;AACA;AASe,SAASA,kBAAT,CAA6B;AAC3CC,EAAAA,SAD2C;AAE3CC,EAAAA,KAAK,GAAG,cAAI,OAAJ,CAFmC;AAG3CC,EAAAA,QAH2C;AAI3CC,EAAAA;AAJ2C,CAA7B,EAKX;AACH,QAAMC,oBAAoB,GAAKC,gBAAF,IAAwB;AACpD,UAAMC,UAAU,GACfD,gBAAgB,KAAK,EAArB,GAA0BE,QAAQ,CAAEF,gBAAF,EAAoB,EAApB,CAAlC,GAA6D,CAD9D;AAEAH,IAAAA,QAAQ,CAAEI,UAAF,CAAR;AACA,GAJD;;AAMA,QAAME,OAAO,GAAG,yBAAY,iCAAZ,EAA+CR,SAA/C,CAAhB;AAEA,SACC,4BAAC,8BAAD;AAAM,IAAA,SAAS,EAAGQ;AAAlB,KACC,4BAAC,eAAD,QACC,4BAAC,qBAAD;AACC,IAAA,KAAK,EAAGP,KADT;AAEC,IAAA,SAAS,EAAC,8CAFX;AAGC,IAAA,GAAG,EAAG,GAHP;AAIC,IAAA,GAAG,EAAG,CAJP;AAKC,IAAA,QAAQ,EAAGG,oBALZ;AAMC,IAAA,IAAI,EAAC,GANN;AAOC,IAAA,KAAK,EAAGD,KAPT;AAQC,IAAA,cAAc,MARf;AASC,IAAA,MAAM,EACL,4BAAC,cAAD;AACC,MAAA,EAAE,EAAGM,UADN;AAEC,MAAA,WAAW,EAAG,kBAAO,CAAP,CAFf;AAGC,MAAA,KAAK,EAAG;AACPC,QAAAA,KAAK,EAAE;AADA;AAHT;AAVF,IADD,CADD,EAwBC,4BAAC,cAAD;AACC,IAAA,KAAK,EAAG;AACPC,MAAAA,UAAU,EAAE,kBAAO,CAAP,CADL;AAEPC,MAAAA,YAAY,EAAE,kBAAO,CAAP,CAFP;AAGPC,MAAAA,SAAS,EAAE;AAHJ;AADT,KAOC,4BAAC,oBAAD;AACC,mBAAY,MADb;AAEC,IAAA,KAAK,EAAGV,KAFT;AAGC,IAAA,QAAQ,EAAGD;AAHZ,IAPD,CAxBD,CADD;AAwCA","sourcesContent":["/**\n * External dependencies\n */\nimport classnames from 'classnames';\n\n/**\n * WordPress dependencies\n */\nimport { __ } from '@wordpress/i18n';\n\n/**\n * Internal dependencies\n */\nimport { FlexBlock, FlexItem } from '../flex';\nimport NumberControl from '../input-control';\nimport AngleCircle from './angle-circle';\nimport { Root } from './styles/angle-picker-control-styles';\nimport { space } from '../ui/utils/space';\nimport { Text } from '../text';\nimport { Spacer } from '../spacer';\n\nexport default function AnglePickerControl( {\n\tclassName,\n\tlabel = __( 'Angle' ),\n\tonChange,\n\tvalue,\n} ) {\n\tconst handleOnNumberChange = ( unprocessedValue ) => {\n\t\tconst inputValue =\n\t\t\tunprocessedValue !== '' ? parseInt( unprocessedValue, 10 ) : 0;\n\t\tonChange( inputValue );\n\t};\n\n\tconst classes = classnames( 'components-angle-picker-control', className );\n\n\treturn (\n\t\t<Root className={ classes }>\n\t\t\t<FlexBlock>\n\t\t\t\t<NumberControl\n\t\t\t\t\tlabel={ label }\n\t\t\t\t\tclassName=\"components-angle-picker-control__input-field\"\n\t\t\t\t\tmax={ 360 }\n\t\t\t\t\tmin={ 0 }\n\t\t\t\t\tonChange={ handleOnNumberChange }\n\t\t\t\t\tstep=\"1\"\n\t\t\t\t\tvalue={ value }\n\t\t\t\t\thideHTMLArrows\n\t\t\t\t\tsuffix={\n\t\t\t\t\t\t<Spacer\n\t\t\t\t\t\t\tas={ Text }\n\t\t\t\t\t\t\tmarginRight={ space( 3 ) }\n\t\t\t\t\t\t\tstyle={ {\n\t\t\t\t\t\t\t\tcolor: 'var( --wp-admin-theme-color )',\n\t\t\t\t\t\t\t} }\n\t\t\t\t\t\t>\n\t\t\t\t\t\t\t°\n\t\t\t\t\t\t</Spacer>\n\t\t\t\t\t}\n\t\t\t\t/>\n\t\t\t</FlexBlock>\n\t\t\t<FlexItem\n\t\t\t\tstyle={ {\n\t\t\t\t\tmarginLeft: space( 4 ),\n\t\t\t\t\tmarginBottom: space( 1 ),\n\t\t\t\t\tmarginTop: 'auto',\n\t\t\t\t} }\n\t\t\t>\n\t\t\t\t<AngleCircle\n\t\t\t\t\taria-hidden=\"true\"\n\t\t\t\t\tvalue={ value }\n\t\t\t\t\tonChange={ onChange }\n\t\t\t\t/>\n\t\t\t</FlexItem>\n\t\t</Root>\n\t);\n}\n"]}