-
Updated
Oct 14, 2021 - JavaScript
component-library
Here are 853 public repositories matching this topic...
A hope
-
Updated
Oct 16, 2021 - JavaScript
<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
-
Updated
Aug 25, 2021 - CSS
-
Updated
Oct 19, 2021 - TypeScript
-
Updated
Oct 19, 2021 - TypeScript
-
Updated
Oct 19, 2021 - TypeScript
-
Updated
Oct 17, 2021 - Vue
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
-
Updated
Aug 6, 2020 - JavaScript
-
Updated
Oct 18, 2021 - JavaScript
-
Updated
Oct 19, 2021 - TypeScript
-
Updated
Oct 19, 2021 - TypeScript
-
Updated
Apr 10, 2021 - JavaScript
-
Updated
Oct 8, 2021 - TypeScript
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-
🚀 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
-
Updated
Oct 19, 2021 - TypeScript
-
Updated
Oct 7, 2021 - TypeScript
-
Updated
Oct 15, 2021 - TypeScript
-
Updated
Oct 5, 2021 - TypeScript
-
Updated
Aug 12, 2021 - JavaScript
-
Updated
Oct 18, 2021 - TypeScript
(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
-
Updated
Aug 6, 2021 - Objective-C
-
Updated
Oct 19, 2021 - Svelte
-
Updated
Oct 19, 2021 - JavaScript
Improve this page
Add a description, image, and links to the component-library topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the component-library topic, visit your repo's landing page and select "manage topics."
hi.
in "react semantic ui" document
search placeholder API is not documented while is implemented for component
please add
tnx