|
2 | 2 |
|
3 | 3 | Reactist follows [semantic versioning](https://semver.org/) and doesn't introduce breaking changes (API-wise) in minor or patch releases. However, the appearance of a component might change in a minor or patch release so keep an eye on redesigns and make sure your app still looks and feels like you expect it. |
4 | 4 |
|
| 5 | +## v7.1.1 |
| 6 | + |
| 7 | +- [Bugfix] Fixes an improperly configured `sideEffects` property in package.json that prevented importing CSS files from reactist. |
| 8 | + |
5 | 9 | ## v7.1.0 |
6 | 10 |
|
7 | | -- [Feature] The tooltip content now can be provided as a function that will be called to generate its content. This function will only be called when the tooltip needs to be shown. This allows to have more control on tooltip content that is potentially expensive to generate, so that it only happens when needed. |
8 | | -- [Fix] The tooltip content is now rendered to the DOM only when the tooltip is shown. This is regardless of wether the content is provided directly or via a function. The React tree won't be comitted to the DOM unless the tooltip needs to become visible. |
9 | | -- [Tweak] The tooltip delay to appear is now extended from 100ms to 500ms which was our earlier standard with the previous implementation of the tooltip. |
| 11 | +- [Feature] The tooltip content now can be provided as a function that will be called to generate its content. This function will only be called when the tooltip needs to be shown. This allows to have more control on tooltip content that is potentially expensive to generate, so that it only happens when needed. |
| 12 | +- [Fix] The tooltip content is now rendered to the DOM only when the tooltip is shown. This is regardless of wether the content is provided directly or via a function. The React tree won't be comitted to the DOM unless the tooltip needs to become visible. |
| 13 | +- [Tweak] The tooltip delay to appear is now extended from 100ms to 500ms which was our earlier standard with the previous implementation of the tooltip. |
10 | 14 |
|
11 | 15 | ## v7.0.0 |
12 | 16 |
|
13 | | -- [BREAKING CHANGE] A new Tooltip component is introduced. It is keyboard and screen reader friendly, more compliant with accessibility recommendations about tooltips. It does not provide all the features of the previous Tooltip, and its props change quite a bit. Additionally, it now has a new restriction where it expects its children to consist of a single element. This element is the one used as a trigger for the tooltip. (#276) |
14 | | -- [BREAKING CHANGE] The `Popover` component now has a new restriction where it expects its children to consist of a single element. (#276) |
15 | | -- [BREAKING CHANGE] A new set of components for building menus is introduced. The new menus are keyboard and screen reader friendly, more compliant with accessibility recommendations about menus. The old `MenuButton` and `MenuButtonItem` components are no longer available. Moreover we now have a `MenuButton` that is nothing like the one before. Check their code and examples in storybook. (#278) |
| 17 | +- [BREAKING CHANGE] A new Tooltip component is introduced. It is keyboard and screen reader friendly, more compliant with accessibility recommendations about tooltips. It does not provide all the features of the previous Tooltip, and its props change quite a bit. Additionally, it now has a new restriction where it expects its children to consist of a single element. This element is the one used as a trigger for the tooltip. (#276) |
| 18 | +- [BREAKING CHANGE] The `Popover` component now has a new restriction where it expects its children to consist of a single element. (#276) |
| 19 | +- [BREAKING CHANGE] A new set of components for building menus is introduced. The new menus are keyboard and screen reader friendly, more compliant with accessibility recommendations about menus. The old `MenuButton` and `MenuButtonItem` components are no longer available. Moreover we now have a `MenuButton` that is nothing like the one before. Check their code and examples in storybook. (#278) |
16 | 20 |
|
17 | 21 | ## v6.0.1 |
18 | 22 |
|
19 | | -- [Fix] This fixes a bug in v6.0.0 where the lib/ directory was unbundled. |
| 23 | +- [Fix] This fixes a bug in v6.0.0 where the lib/ directory was unbundled. |
20 | 24 |
|
21 | 25 | ## v6.0.0 |
22 | 26 |
|
23 | | -- [BREAKING CHANGE] Reactist now generates a build more aligned to antd's best practices. It generates a clean ES6 build, a CommonJS build, as well as an unpkg build. It also adds built-in support for future CSS module integration. This is a breaking change because importing modules has changed slightly. See README.md. |
24 | | -- [BREAKING CHANGE] The `Button` component's `close` prop, which was deprecated back in v5, is now no longer supported. |
| 27 | +- [BREAKING CHANGE] Reactist now generates a build more aligned to antd's best practices. It generates a clean ES6 build, a CommonJS build, as well as an unpkg build. It also adds built-in support for future CSS module integration. This is a breaking change because importing modules has changed slightly. See README.md. |
| 28 | +- [BREAKING CHANGE] The `Button` component's `close` prop, which was deprecated back in v5, is now no longer supported. |
25 | 29 |
|
26 | 30 | ## v5.2.0 |
27 | 31 |
|
28 | | -- [Feature] `Button` can now be unstyled if you omit the `variant` prop. This resets the styles to be even less than default styles of the web browser (e.g. removes all border, padding and background). |
| 32 | +- [Feature] `Button` can now be unstyled if you omit the `variant` prop. This resets the styles to be even less than default styles of the web browser (e.g. removes all border, padding and background). |
29 | 33 |
|
30 | 34 | ## v5.1.0 |
31 | 35 |
|
32 | | -- [New] A `KeyboardShortcut` component will take one or several keyboard shortcut specified as string, and will parse them and render them in a nice semantic markup using the `kbd` element. Each key part of a key combination gets its own container so you can style things nicely. |
| 36 | +- [New] A `KeyboardShortcut` component will take one or several keyboard shortcut specified as string, and will parse them and render them in a nice semantic markup using the `kbd` element. Each key part of a key combination gets its own container so you can style things nicely. |
33 | 37 |
|
34 | 38 | ## v5.0.0 |
35 | 39 |
|
|
0 commit comments