Progress tracker
A progress tracker displays the steps and progress through a journey.
yarn add @atlaskit/progress-tracker
10.0.2
Patch Changes
- Updated dependencies
A progress tracker displays the steps and progress through a journey.
yarn add @atlaskit/progress-tracker
#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 v1808728da34c4fd
-
The step marker for disabled steps has been updated to use the disabled icon color token. This
change is no longer behind a feature flag.057afb45671d1
-
[ux] The step marker for disabled steps has been updated to use the disabled icon color token.103e97b52f101
-
Removes feature flag removing internal use of the legacy NodeResolver package in favor of react
refs#171836
30eff06f3753e
-
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/progress-tracker
, 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.
5c6ea433574d2
-
We are testing changes behind a feature gate. Progress tracker steps have been updated to use
automatic router link configuration (from App provider). If this change is successful it will be
available in a later release.5eb2a70adb262
-
Remove react-router-dom from devDependencies as it is incompatible with React 18.57f451bda8919
-
Adds side-effect config to support Compiled css extraction in third-party appsfddbc0849871c
-
DSP-21285 replacing platform-design-system-dsp-20687-transition-group with
platform_design_system_team_transition_group_r188b5cef4cf858b
-
Removal of FF platform-progress-tracker-functional-facade which was added during the functional
component conversion2bbc16219edd2
-
[ux] Disabled, visited and current step indicator font weight change from semibold to bold.2d1da097bd763
-
DSP-20687 removing usage of findDOMNode in react-transition-group behind ff7e834d0456744
-
Converting ProgressTracker component from class component to functional component#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.
798a9f4b8913d
-
Updated styling to ensure bullet point styles aren't added when rendered in certain UI Kit
extensions points.a8bd419fd70b9
-
Explicitly set jsxRuntime to classic via pragma comments in order to avoid issues where jsxRuntime
is implicitly set to automatic.57f9d0819e9e6
-
Internal change only. Update spacing to use logical properties and tokenise typography values.7cce9cbf2f08
-
Internal changes to how text is rendered. There is no expected visual change.6ab9799d402
- The
internal composition of this component has changed. There is no expected change in behavior.fd6bb9c9184
- Delete
version.json56507598609
- Skip
minor dependency bump2e01c9c74b5
- DUMMY
remove before merging to master; dupe adf-schema via adf-utilscfe48bb7ece
- Internal
change only. Replace usages of Inline/Stack with stable version from @atlaskit/primitives
.18aeca8c199
- Internal
change to update token references. There is no expected behaviour or visual change.4ee60bafc6d
-
ED-16603: Remove tooltips from VR tests and make them opt in. To opt-in, add allowedSideEffects
when loading the page.eadbf13d8c0
- Updated
usages of Text
, Box
, Stack
, and Inline
primitives to reflect their updated APIs. There are
no visual or behaviour changes.eb709e1fde3
- [ux]
Apply spacing tokens and primitive components. Reduce padding between stage labels and progress
bar by 4px - overall height of component is therefore also 4px shorter.bc989043572
- Internal
changes to apply spacing tokens. This should be a no-op change.9827dcb82b8
- No-op
change to introduce spacing tokens to design system components.099a8b4949e
- Updates
@emotion/core
to @emotion/react
; v10 to v11. There is no expected behavior change.#19019
4e96270c06e
- [ux]
Instrumented progress-tracker 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.
d2429272ffa
- Migrates
usage of styled-components
to @emotion
. Under the hood the component also no longer uses
@atlaskit/page/grid
, although still uses the same spacing scale.b90c0237824
- Update
package.jsons to remove unused dependencies.8ae29c21d55
- Removed
the !important
declaration from the top margin style.3e1d0e22b98
- [ux]
Marked a progress tracker wrapper as unordered list. Step component wrapper has been changed to li
tag for each step. Added label prop that is used as aria-label.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.
954cc87b62
- The readme
and package information has been updated to point to the new design system website.87f4720f27
- 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]8ca2bfc206:
Change imports to comply with Atlassian conventions- Updated dependencies 443bb984ab:
Updated dependencies 6b8e60827e:
Updated dependencies 449ef134b3:
Updated dependencies 57c0487a02:
[patch]6548261c9a:
Remove namespace imports from React, ReactDom, and PropTypes- Updated dependencies 6548261c9a:
[patch]a70bb511fc:
Fixes an issue with how ProgressTracker deals with stages being added or removed- [patch]4a223473c5:
Removes babel/runtime from dependencies. Users should see a smaller bundlesize as a result- Updated dependencies 28f8f0e089:
Updated dependencies 82747f2922:
Updated dependencies 4a223473c5:
[patch]35d2229b2a:
Adding missing license to packages and update to Copyright 2019 Atlassian Pty Ltd.
[minor]c6efb2f5b6:
Prefix the legacy lifecycle methods with UNSAFE_* to avoid warning in React 16.9+
More information about the deprecation of lifecycles methods can be found here: https://reactjs.org/blog/2018/03/29/react-v-16-3.html#component-lifecycle-changes
[patch]4432d729b7:
@atlaskit/progress-tracker 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]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
[patch]202fda1d9e:
Moved dependencies to devDependencies in progress-tracker: move 'react-dom' to devDependencies.
[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.