An empty state appears when there is no data to display and describes what the user can do next.
yarn add @atlaskit/empty-state#117363
10a0f7f6c2027 -
This package's peerDependencies have been adjusted for react and/or react-dom to reflect the
status of only supporting React 18 going forward. No explicit breaking change to React support has
been made in this release, but this is to signify going forward, breaking changes for React 16 or
React 17 may come via non-major semver releases.
Please refer this community post for more details: https://community.developer.atlassian.com/t/rfc-78-dropping-support-for-react-16-and-rendering-in-a-react-18-concurrent-root-in-jira-and-confluence/87026
b50c5d5d65ae2 -
Bump to the latest version of @compiled/react4660ec858a305 -
Update React from v16 to v18c9ff1f8d5e9ca -
Migrated from primitives components to primitives/compiled components#162676
6dd54dec02a69 -
Migrated from @emotion/react to @compiled/react in order to improve performance, align with
the rest of the Atlaskit techstack, and support React 18 Streaming SSR.
Please note, in order to use this version of @atlaskit/empty-state, you will need to ensure that
your bundler is configured to handle .css imports correctly. Most bundlers come with built-in
support for .css imports, so you may not need to do anything. If you are using a different
bundler, please refer to the documentation for that bundler to understand how to handle .css
imports.
For more information on the migration, please refer to RFC-73 Migrating our components to Compiled CSS-in-JS.
57f451bda8919 -
Adds side-effect config to support Compiled css extraction in third-party apps745cc262139e7 -
[ux] Removed feature flag platform.design-system-team.empty-state-typography-updates_gndrj
resultingin fully tokenised typography styles.5d414827c3394 -
Removes usages of deprecated CustomThemeButton in favor of the new Button1d43605b39f55 -
We are testing a visual change behind a feature flag inceasing specificity of description
typography styles. If this change is successful it will be available in a later release.#127511
db30e29344013 -
Widening range of react and react-dom peer dependencies from ^16.8.0 || ^17.0.0 || ~18.2.0
to the wider range of ``^16.8.0 || ^17.0.0 || ^18.0.0` (where applicable).
This change has been done to enable usage of react@18.3 as well as to have a consistent peer
dependency range for react and react-dom for /platform packages.
1bb99c2a69e9c -
We are testing a visual change behind a feature flag. The letter spacing of empty state title
changes. If this change is successful it will be available in a later release.223959ef57c80 -
Explicitly set jsxRuntime to classic via pragma comments in order to avoid issues where jsxRuntime
is implicitly set to automatic.b037e5451037 -
Update new button text color fallback for default theme (non-token) to match that of old button
current text colorf1279b936714 -
[ux] Button group inside empty-state now have default label and possibility to accept a dynamic
one.4ae083a7e66 - Use
@af/accessibility-testing for default jest-axe config and jest-axe import in accessibility
testing.56d11ec914b - Add a
new prop headingLevel to set the heading level in the header element.56507598609 - Skip
minor dependency bump261420360ec - Upgrades
component types to support React 18.74c1b81a476 - Replaces
use of gridSize with space tokens. There is no expected visual change.24f81932945 - Migrates
unit tests from enzyme to RTL. Adds testId to Spinner component.18aeca8c199 - Internal
change to update token references. There is no expected behaviour or visual change.bc989043572 - Internal
changes to apply spacing tokens. This should be a no-op change.9de88fa1e1e - Internal
changes to include spacing tokens in component implementations.645ec6a64a8 - Updates
@emotion/core to @emotion/react; v10 to v11. There is no expected behavior change.19d72473dfb - Updates
usage of deprecated token names so they're aligned with the latest naming conventions. No UI or
visual changesf460cc7c411 - Builds
for this package now pass through a tokens babel plugin, removing runtime invocations of the
tokens() function and improving bundle size.#14319
b5c96b26bf3 -
Instrumented empty-state with the new theming package, @atlaskit/tokens.
New tokens will be visible only in applications configured to use the new Tokens API (currently in alpha). These changes are intended to be interoperable with the legacy theme implementation. Legacy dark mode users should expect no visual or breaking changes.
7465c0f0e1d - Fix to
account for the size/width fallback behaviour. Previously if a user provided a value for the the
width property it would always be ignored, this is no longer the case.#13864
20ea31c9fdf -
Deprecation Warning The size prop and Sizes type have been flagged as deprecated. Both are
better described as a width and so internally have been renamed. The size prop will continue to
work in the shortrun before it's formally removed in the component's next major release.
Housekeeping:
331c29990c9 - Removes
styled-components as a peer dependency in favour of a direct dependency on emotion.5f58283e1f - Export
types using Typescript's new "export type" syntax to satisfy Typescript's --isolatedModules
compiler option. This requires version 3.8 of Typescript, read more about how we handle Typescript
versions here: https://atlaskit.atlassian.com/get-started Also add typescript to
devDependencies to denote version that the package was built with.#3885
6c525a8229 - Upgraded
to TypeScript 3.9.6 and tslib to 2.0.0
Since tslib is a dependency for all our packages we recommend that products also follow this tslib upgrade to prevent duplicates of tslib being bundled.
22aa614abb - Introduce
optional renderImage prop which will be displayed if no imageUrl is provided3414523d6f - Rearange
buttons order to align with design guidelinesdb053b24d8 - Update all
the theme imports to be tree-shakable87f4720f27 - Officially
dropping IE11 support, from this version onwards there are no warranties of the package working in
IE11. For more information see:
https://community.developer.atlassian.com/t/atlaskit-to-drop-support-for-internet-explorer-11-from-1st-july-2020/3953454a9514fcf - Build and
supporting files will no longer be published to npm[patch]f4374a322a:
Change imports to comply with Atlassian conventions- Updated dependencies 6b8e60827e:
Updated dependencies 57c0487a02:
[patch]c5182f1c53:
Widens the accepted Types for description to include any react node- Updated dependencies dae900bf82:
Updated dependencies 8c9e4f1ec6:
[patch]6548261c9a:
Remove namespace imports from React, ReactDom, and PropTypes- Updated dependencies 6548261c9a:
[patch]6c9c2d5487:
Fixes empty state image not having appropriate accessibility attributes.- Updated dependencies 3c0f6feee5:
Updated dependencies f9c291923c:
[patch]35d2229b2a:
Adding missing license to packages and update to Copyright 2019 Atlassian Pty Ltd.
[patch]097b696613:
Components now depend on TS 3.6 internally, in order to fix an issue with TS resolving non-relative imports as relative imports
[patch]708028db86:
Change all the imports to theme in Core to use multi entry points
[major]433311c16a:
@atlaskit/empty-state has been converted to Typescript. Typescript consumers will now get static type safety. Flow types are no longer provided. No API or behavioural changes.
[patch]b0ef06c685:
[major]7c17b35107:
[patch]98e11001ff:
[major]76299208e6:
As a breaking change, all @atlaskit packages will be dropping cjs distributions and will only
distribute esm. This means all distributed code will be transpiled, but will still contain
import and export declarations.
The major reason for doing this is to allow us to support multiple entry points in packages, e.g:
import colors from `@atlaskit/theme/colors`;
Previously this was sort of possible for consumers by doing something like:
import colors from `@atlaskit/theme/dist/esm/colors`;
This has a couple of issues. 1, it treats the file system as API making internal refactors harder, we have to worry about how consumers might be using things that aren't actually supposed to be used. 2. We are unable to do this internally in @atlaskit packages. This leads to lots of packages bundling all of theme, just to use a single color, especially in situations where tree shaking fails.
To support being able to use multiple entrypoints internally, we unfortunately cannot have multiple distributions as they would need to have very different imports from of their own internal dependencies.
ES Modules are widely supported by all modern bundlers and can be worked around in node environments.
We may choose to revisit this solution in the future if we find any unintended condequences, but we see this as a pretty sane path forward which should lead to some major bundle size decreases, saner API's and simpler package architecture.
Please reach out to #fabric-build (if in Atlassian) or create an issue in Design System Support (for external) if you have any questions or queries about this.