Official React components built for Flowbite and Tailwind CSS
MIT License
Bot releases are hidden (Show)
Published by rluders over 1 year ago
See #547
<Progress label={}>
-> <Progress textLabel={}>
<Progress labelPosition={}>
-> <Progress progressLabelPosition={} textLabelPosition={}>
target
to Button
props to open a link in new tab by @fsioni in https://github.com/themesberg/flowbite-react/pull/631
ReferenceError: window is not defined
error with Next.js by @fsioni in https://github.com/themesberg/flowbite-react/pull/652
Full Changelog: https://github.com/themesberg/flowbite-react/compare/v0.4.1...v0.4.2
Published by tulup-conner over 1 year ago
Full Changelog: https://github.com/themesberg/flowbite-react/compare/v0.4.0...v0.4.1
Published by tulup-conner over 1 year ago
usePreferences
usePreferences
is no longer an option for <Flowbite theme={..}>
. The light or dark mode preference established by a user's browser is still respected. The library also no longer persists the current theme in local storage. See #582
flowbite-react
The theme structure for almost all components has changed. Now, components that can have children will have a root
section which contains the classes that apply only to the parent component. That's kind of a complicated sentence, so here's an example.
<Accordion>
s can contain any number of <Accordion.Title>
s and <Accordion.Content>
s as children. The new accordion theme looks like:
export interface FlowbiteAccordionTheme {
root: FlowbiteAccordionRootTheme; /* classes that apply to <Accordion> itself only */
content: FlowbiteAccordionComponentTheme; /* <Accordion.Content> classes */
title: FlowbiteAccordionTitleTheme; /* <Accordion.Title> classes */
}
Previously, the accordion theme was:
export interface FlowbiteAccordionTheme {
base: string; /* class that applies to <Accordion> itself only */
flush: string; /* another class that applies to <Accordion>s */
content: FlowbiteAccordionComponentTheme; /* <Accordion.Content> classes */
title: FlowbiteAccordionTitleTheme; /* <Accordion.Title> classes */
}
We've just moved the loose classes - for <Accordion>
s, that's accordion.base
and accordion.flush
- into root
to make the theme more clearly reflect the relationship between flowbite-react
components.
theme={}
attribute to components that need it by @tulup-conner in https://github.com/themesberg/flowbite-react/pull/611
usePreferences
by @haron68 in https://github.com/themesberg/flowbite-react/pull/582
{' '}
literals from code examples by @tulup-conner in https://github.com/themesberg/flowbite-react/pull/614
<Alert>
s by @lirbre in https://github.com/themesberg/flowbite-react/pull/586
README
by @tulup-conner in https://github.com/themesberg/flowbite-react/pull/615
<Badge>
s by @lirbre in https://github.com/themesberg/flowbite-react/pull/617
flowbite-react
Completing our work in v0.3.7 and v0.3.8, the following components can now be customized with a theme={}
attribute inline:
Please note that components you do NOT see on this list can STILL be customized by simply adding a className
. These components do not have any default classes or complex structure and thus don't need a theme at all.
We updated the documentation on themes to clarify the different options you have to customize flowbite-react
. To learn more about that, visit https://flowbite-react.com/theme.
This behavior is still considered a work in progress, and in general, we are still experimenting with how to provide users with the best way to customize components. You can expect that this API might change at any time. We also need your feedback on how to improve it.
See #465 for more context on themes in this library.
Full Changelog: https://github.com/themesberg/flowbite-react/compare/v0.3.8...v0.4.0