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

🚀 Feature request

Is your feature request related to a problem?

Long menu items don't fit in the side-menu

Describe the solution you'd like

Perhaps we should show each menu item in one line with elipsis, or make it customizable

Additional context

Bug type

Component

Component name

MudDateRangePicker and MudDatePicker

What happened?

Setting the culture of the MudDateRangePicker or the MudDatePicker doesn't properly set the Culture of the Component and the default settings are still shown.

This can be seen in the example, were the format patter stays MM/dd/yyyy eventhoug the culture defines the format as yyyy-MM-

(moved over from https://github.com/github/design-systems/issues/860, thanks @smockle 👋 !)

Problem

Occasionally it’s useful to add an interactive element with the semantics of button (correctly represented in the AT)—but without its visual styles.

Solution

Other teams at GitHub spread the following object in sx props to destyle Buttons:

// Removes most of 'button'’s visual appearanc