react-components
Here are 2,843 public repositories matching this topic...
-
Updated
Mar 14, 2021
-
Updated
Mar 30, 2021 - JavaScript
-
Updated
Mar 31, 2021 - JavaScript
-
Updated
Mar 31, 2021 - JavaScript
-
Updated
Mar 31, 2021 - TypeScript
hi.
in "react semantic ui" document
search placeholder API is not documented while is implemented for component
please add
tnx
-
Updated
Mar 31, 2021 - TypeScript
-
Updated
Mar 9, 2021 - TypeScript
-
Updated
Mar 8, 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
Mar 31, 2021 - TypeScript
-
Updated
Mar 31, 2021 - TypeScript
-
Updated
Dec 30, 2020 - TypeScript
-
Updated
Mar 25, 2021 - Ruby
🐛 Bug Report
🤔 Expected Behavior
General input event handlers are triggered appropriately
 {
const message = plural(5, {
other: '# + #
})
return <p>{message}</p>
}-
Updated
Mar 30, 2021 - JavaScript
-
Updated
Aug 6, 2020 - JavaScript
-
Updated
Sep 4, 2020 - JavaScript
-
Updated
Mar 2, 2021 - JavaScript
-
Updated
Mar 12, 2021 - JavaScript
-
Updated
Mar 30, 2021 - JavaScript
Improve this page
Add a description, image, and links to the react-components topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the react-components topic, visit your repo's landing page and select "manage topics."
At the moment in PaginationItem I can set common styles in the styles.root.
These can be overwritten by styles.page (if you do not use (props: PaginationItemProps)).
However material also adds the page styles to the next and previous button. Preventing you from styling those seperately from the page buttons. I would like it that the next and previous button would not have the page styles in t