feat(ds-core-form): boilerplate pt 4

[advl]

Done

• Adds Range Input
• Adds native Select Input
• Adds SimpleChoices input (fieldset of radios/comboboxes)
• Adds useOptionAriaProperties hook in an initial stage
• Fixes useFieldAriaProperties call of useId
• Enhances props of components with a union to native HTML properties (e.g. export type TextareaProps = BaseInputProps & React.HTMLProps<HTMLTextAreaElement>; )
• drive_by: Added a note about the autodocs on the storybook package

QA

• ! Atm, there are a bunch of type errors. Not ready for final Q/A yet.

PR readiness check

• PR should have one of the following labels:
  • Feature 🎁, Breaking Change 💣, Bug 🐛, Documentation 📝, Maintenance 🔨.
• PR title follows the Conventional Commits format.
• All packages define the required scripts in package.json:
  • All packages: check, check:fix, and test.
  • Packages with a build step: build.

[advl]

Points of interest for an initial review :

• Type enhancements for component props (native html props)
• Usage of Fieldset for the SimpleChoices component
• Usage of a javascript-read value in the output tag of the Range input
• the useOptionAriaProperties hooks

[jmuzina]

I noticed that the output is currently empty until the user changes the slider value (no initial value is loaded).

Even when I modified the range story to use a pre-filled value, the output was not populated until after I interacted with the form.

[advl]

fixed
a dictionary of defaultValues needs to be provided to the Form at instantiation - see the story on the latest commit for an example

[advl]

a dictionary of defaultValues needs to be provided to the Form at instantiation - see the story on the latest commit for an example

[jmuzina]

Ah, I was consuming the form in an unintended way I think:

<Field type="range" value={3}/>

value is valid here as it comes from the InputElement props. You may want to disallow that prop if we don't intend for the field to be used in this way.