Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

InputControl: Improve type annotations and stories #40119

Merged
merged 9 commits into from
Apr 12, 2022
Merged
Show file tree
Hide file tree
Changes from 7 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions packages/components/CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,7 @@
- Update `BorderControl` and `BorderBoxControl` to allow the passing of custom class names to popovers ([#39753](https://github.com/WordPress/gutenberg/pull/39753)).
- `ToggleGroupControl`: Reintroduce backdrop animation ([#40021](https://github.com/WordPress/gutenberg/pull/40021)).
- `Card`: Adjust border radius effective size ([#40032](https://github.com/WordPress/gutenberg/pull/40032)).
- `InputControl`: Improved TypeScript type annotations ([#40119](https://github.com/WordPress/gutenberg/pull/40119)).

### Internal

Expand Down
4 changes: 2 additions & 2 deletions packages/components/src/input-control/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -105,5 +105,5 @@ Type of the input element to render. Defaults to "text".

The current value of the input.

- Type: `String | Number`
- Required: Yes
- Type: `String`
- Required: No
25 changes: 22 additions & 3 deletions packages/components/src/input-control/index.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ function useUniqueId( idProp?: string ) {
return idProp || id;
}

export function InputControl(
export function UnforwardedInputControl(
{
__unstableStateReducer: stateReducer = ( state ) => state,
__unstableInputWidth,
Expand Down Expand Up @@ -88,6 +88,25 @@ export function InputControl(
);
}

const ForwardedComponent = forwardRef( InputControl );
/**
* InputControl components let users enter and edit text. This is an experimental component
* intended to (in time) merge with or replace `TextControl`.
*
* @example
* import { __experimentalInputControl as InputControl } from '@wordpress/components';
* import { useState } from '@wordpress/compose';
*
* const Example = () => {
* const [ value, setValue ] = useState( '' );
*
* return (
* <InputControl
* value={ value }
* onChange={ ( nextValue ) => setValue( nextValue ) }
* />
* );
* };
*/
export const InputControl = forwardRef( UnforwardedInputControl );

export default ForwardedComponent;
export default InputControl;
3 changes: 2 additions & 1 deletion packages/components/src/input-control/input-base.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,7 @@ import {
LabelWrapper,
} from './styles/input-control-styles';
import type { InputBaseProps, LabelPosition } from './types';
import type { FlexProps } from '../flex/types';

function useUniqueId( idProp?: string ) {
const instanceId = useInstanceId( InputBase );
Expand Down Expand Up @@ -65,7 +66,7 @@ export function InputBase(
size = 'default',
suffix,
...props
}: InputBaseProps,
}: InputBaseProps & FlexProps,
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe this is the correct placement of FlexProps. See a682653

Copy link
Contributor

@ciampo ciampo Apr 7, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that normally we have "merged" prop types in the types.ts file (similarly to how the code was before the changes in this PR).

Is the reason for this to avoid that InputControlProps inherits FlexProps from InputBaseProps ? I wonder if those FlexProps were ever passed to InputControl (in that case, removing them could be seen as a breaking change?)

Copy link
Member Author

@mirka mirka Apr 8, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that normally we have "merged" prop types in the types.ts file (similarly to how the code was before the changes in this PR).

Ah ok, I'll keep the logic in the types.ts file. 53b7e08

Is the reason for this to avoid that InputControlProps inherits FlexProps from InputBaseProps ?

Correct 👍

I verified that any FlexProps passed to InputControl would have been passed through (via ...props) to an <input>, where they would have no effect. So I think we're ok.

ref: ForwardedRef< HTMLDivElement >
) {
const id = useUniqueId( idProp );
Expand Down
71 changes: 0 additions & 71 deletions packages/components/src/input-control/stories/index.js

This file was deleted.

63 changes: 63 additions & 0 deletions packages/components/src/input-control/stories/index.tsx
Original file line number Diff line number Diff line change
@@ -0,0 +1,63 @@
/**
* External dependencies
*/
import type { ComponentMeta, ComponentStory } from '@storybook/react';

/**
* Internal dependencies
*/
import InputControl from '..';

const meta: ComponentMeta< typeof InputControl > = {
title: 'Components (Experimental)/InputControl',
component: InputControl,
argTypes: {
__unstableInputWidth: { control: { type: 'text' } },
__unstableStateReducer: { control: { type: null } },
onChange: { control: { type: null } },
prefix: { control: { type: null } },
suffix: { control: { type: null } },
type: { control: { type: 'text' } },
},
parameters: {
controls: { expanded: true },
docs: { source: { state: 'open' } },
},
};
export default meta;

const Template: ComponentStory< typeof InputControl > = ( args ) => (
<InputControl { ...args } />
);

export const Default = Template.bind( {} );
Default.args = {
label: 'Value',
placeholder: 'Placeholder',
value: '',
};

export const WithPrefix = Template.bind( {} );
WithPrefix.args = {
...Default.args,
prefix: <span style={ { paddingLeft: 8 } }>@</span>,
};

export const WithSuffix = Template.bind( {} );
WithSuffix.args = {
...Default.args,
suffix: <button style={ { marginRight: 4 } }>Send</button>,
};

export const WithSideLabel = Template.bind( {} );
WithSideLabel.args = {
...Default.args,
labelPosition: 'side',
};

export const WithEdgeLabel = Template.bind( {} );
WithEdgeLabel.args = {
...Default.args,
__unstableInputWidth: '20em',
labelPosition: 'edge',
};
67 changes: 65 additions & 2 deletions packages/components/src/input-control/types.ts
Original file line number Diff line number Diff line change
Expand Up @@ -7,14 +7,14 @@ import type {
ChangeEvent,
SyntheticEvent,
PointerEvent,
HTMLInputTypeAttribute,
} from 'react';
import type { useDrag } from '@use-gesture/react';

/**
* Internal dependencies
*/
import type { StateReducer } from './reducer/state';
import type { FlexProps } from '../flex/types';
import type { WordPressComponentProps } from '../ui/context';

export type LabelPosition = 'top' | 'bottom' | 'side' | 'edge';
Expand All @@ -27,9 +27,24 @@ export type Size = 'default' | 'small' | '__unstable-large';

interface BaseProps {
__unstableInputWidth?: CSSProperties[ 'width' ];
/**
* If true, the label will only be visible to screen readers.
*
* @default false
*/
hideLabelFromVision?: boolean;
isFocused: boolean;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we also add docs for isFocused (including the false default value) ?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure thing. Does this description look correct? 128618a

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, looks good!

/**
* The position of the label.
*
* @default 'top'
*/
labelPosition?: LabelPosition;
/**
* Adjusts the size of the input.
*
* @default 'default'
*/
size?: Size;
}

Expand All @@ -39,30 +54,78 @@ export type InputChangeCallback<
> = ( nextValue: string | undefined, extra: { event: E } & P ) => void;

export interface InputFieldProps extends BaseProps {
/**
* Determines the drag axis.
*
* @default 'n'
*/
dragDirection?: DragDirection;
/**
* If `isDragEnabled` is true, this controls the amount of `px` to have been dragged before
* the drag gesture is actually triggered.
*
* @default 10
*/
dragThreshold?: number;
/**
* If true, enables mouse drag gestures.
*
* @default false
*/
isDragEnabled?: boolean;
/**
* If true, the `ENTER` key press is required in order to trigger an `onChange`.
* If enabled, a change is also triggered when tabbing away (`onBlur`).
*
* @default false
*/
isPressEnterToChange?: boolean;
/**
* A function that receives the value of the input.
*/
onChange?: InputChangeCallback;
onValidate?: (
nextValue: string,
event?: SyntheticEvent< HTMLInputElement >
) => void;
setIsFocused: ( isFocused: boolean ) => void;
stateReducer?: StateReducer;
/**
* The current value of the input.
*/
value?: string;
onDragEnd?: ( dragProps: DragProps ) => void;
onDragStart?: ( dragProps: DragProps ) => void;
onDrag?: ( dragProps: DragProps ) => void;
Comment on lines 105 to 107
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We're lacking in documentation for the drag stuff overall 😓 I'd say it's low priority though.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, that's not an easy one because we want to be careful to document it in a way that doesn't necessarily expose the @use-gesture/react library as a dependency, in case we want to swap it in the future.

Copy link
Contributor

@ciampo ciampo Apr 7, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Currently the generated type for these props is a bit convoluted ((dragProps: Omit<FullGestureState<"drag">, "event"> & { event: unknown; }) => void), do you think it's ok to keep it as-is, or should we try to simplify it at least for the docs description?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Honestly I don't know what that "simplified" version would be 😅 I'm fine with keeping it as is for now, because it's probably irrelevant for 99% of consumers, at least without proper documentation.

Also TIL you can override type info in the args table. Nice option to have (when it's worth the maintenance cost)!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed, let's keep it as-is and improve it later if/when necessary

Also TIL you can override type info in the args table. Nice option to have (when it's worth the maintenance cost)!

That's very useful, definitely good to know!

/**
* Type of the input element to render.
*
* @default 'text'
*/
type?: HTMLInputTypeAttribute;
}

export interface InputBaseProps extends BaseProps, FlexProps {
export interface InputBaseProps extends BaseProps {
children: ReactNode;
/**
* Renders an element on the left side of the input.
*/
prefix?: ReactNode;
/**
* Renders an element on the right side of the input.
*/
suffix?: ReactNode;
/**
* If true, the `input` will be disabled.
*
* @default false
*/
disabled?: boolean;
className?: string;
id?: string;
/**
* If this property is added, a label will be generated using label property as the content.
*/
label?: ReactNode;
}

Expand Down