hi.
in "react semantic ui" document
search placeholder API is not documented while is implemented for component
please add
tnx

I hope that all component reference docs indicates the name of component for referencing at the header, just like Vant:

Thanks a lot.

<Select /> and <DatePicker /> don't offer the option of accessing name, id and other props once the onChange handler triggers. An event object with this information is accessible in the onChange handler for <Input />.

Feature description

Provide access to these variables for Select and DatePicker. It is needed when the component is being passed handler functions from an

The DatePicker component is already created and it's functional, but it was written some time ago and it can be refactored (migrating from class-based to hooks). In order to achieve a good result, we also need a good test coverage.

Running storyb

Suggested technology

- What technology do you suggest we start using?
Type System, TypeScript

- What problem does it solve?
Having type system inside Circuit UI we want to solve problems like:

1. Strict typing
   Everything stays the way we define it. Need a variable to always be a number? It’ll always be a number, then.

2. Structural typing
   In