Expose DateInput component

[marcopiii]

No description provided.

[veej]

Thanks 🙏
Just a couple of minor doubts inline

[veej]

Is this correct? Is there a specific reason to ignore the validationState when used as a standalone component?

[marcopiii]

I did it becausevalidationState is relevant only for the field part, the standalone component doesn't use it

bento-design-system/packages/bento-design-system/src/DateField/Input.tsx

Lines 31 to 43 in c5f26ca

	type Props = (
	| { type: "single"; fieldProps: AriaDatePickerProps<DateValue> }
	| {
	type: "range";
	fieldProps: {
	start: AriaDatePickerProps<DateValue>;
	end: AriaDatePickerProps<DateValue>;
	};
	}
	) & {
	buttonProps: AriaButtonProps<"button">;
	isCalendarOpen: boolean;
	};

Should we also add it to the standalone component? It would be coherent with NumberInput actually

[veej]

🤔 I see the internalProps including it are passed only to useDatePicker and useDatePickerState which, according to the documentation, don't take a validationState. So I think it's irrelevant 👍

[veej]

can't we just expose the datePicker as a DateInput component and then define the DateField as another component wrapping the DateInput?

[marcopiii]

That was my first approach, but the useDatePicker hook returns stuff that is necessary both for the input and the field. If we separate them into two components, wouldn't we have to use useDatePicker both in DateInput and DateField?

[veej]

👏