A progress indicator shows the user where they are along the steps of a journey.
yarn add @atlaskit/progress-indicator#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 v1857f451bda8919 -
Adds side-effect config to support Compiled css extraction in third-party apps8b29068863297 -
[ux] Update background color of progress indicator dotsa3aec4aa82255 -
Add border for progress indicator dots to increase color contrast47c7e60baaa05 -
Removes the small size from the size prop. Using the small size contributed to accessibility
issues and was unused in the majority of Atlassian products.#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.
a8bd419fd70b9 -
Explicitly set jsxRuntime to classic via pragma comments in order to avoid issues where jsxRuntime
is implicitly set to automatic.6cca90095b7e -
[ux] - Fixes a bug where progress indicator dots are not focusable in the tab order.
Pressable primitive.35fd5ed8e1d7 -
Upgrading internal dependency bind-event-listener to @^3.0.0b037e5451037 -
Update new button text color fallback for default theme (non-token) to match that of old button
current text color48b3b440f51 - Removed
all remaining legacy theming logic from the Icon and ProgressIndicator components.a2a52116171 - Remove
role=tablist when progress indicator is not interactive4ce6b505282 - The
internal composition of this component has changed. There is no expected change in behavior.fd6bb9c9184 - Delete
version.json4ae083a7e66 - Use
@af/accessibility-testing for default jest-axe config and jest-axe import in accessibility
testing.599bfe90ee3 - Internal
change to use shape tokens. There is no expected visual change.e7ea6832ad2 - Bans the
use of React.FC/React.FunctionComponent type in ADS components as part of the React 18 migration
work. The change is internal only and should not introduce any changes for the component
consumers.56507598609 - Skip
minor dependency bump2e01c9c74b5 - DUMMY
remove before merging to master; dupe adf-schema via adf-utils261420360ec - Upgrades
component types to support React 18.cfe48bb7ece - Internal
change only. Replace usages of Inline/Stack with stable version from @atlaskit/primitives.842bb999a85 - 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.eadbf13d8c0 - Updated
usages of Text, Box, Stack, and Inline primitives to reflect their updated APIs. There are
no visual or behaviour changes.767258f2c53 - Set main
container of progress indicator as display block instead of flex given display flex is now set on
the direct child of the main containerc146611a18c - [ux]
Migrate progress-indicator package to use spacing primitives to control spacing in both component
and examples. Spacing values have been slightly updated depending on indicator size and spacing
properties9827dcb82b8 - No-op
change to introduce spacing tokens to design system components.b85b29dd351 - Updates
@emotion/core to @emotion/react; v10 to v11. There is no expected behavior change.8a5bdb3c844 -
Upgrading internal dependency (bind-event-listener) for improved internal typese4b612d1c48 - Internal
migration to bind-event-listener for safer DOM Event cleanup#18526
303e4bf4aa5 - [ux]
Instrumented progress-indicator 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.
58884c2f6c1 - Internal
code change turning on a new linting rule.2b2290121eb - Raised
the minimum version carat range of focus ring to latest.7d89d624097 - Fix for
focus being incorrectly retained when indicators were not interactive.#14319
947ba5b11f0 - The
component has undergone an internal refactor. The following changes need to be called out:
styled-components has been removed from the package in favour of @emotion/core.testId prop in line with other Design System components. This can
be used for automated testing.79c23df6340 - Use
injected package name and version for analytics instead of version.json.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.2b345b4e66 - Renamed
default export of @atlaskit/progress-indicator to ProgressIndicator and have added codemod for
renaming ProgressDots to ProgressIndicator.#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]6548261c9a:
Remove namespace imports from React, ReactDom, and PropTypes- Updated dependencies 6548261c9a:
[patch]24865cfaff:
Fixes Dots onSelect prop return type to void- Updated dependencies 24865cfaff:
Updated dependencies 24865cfaff:
[patch]d222c2b987:
Theme has been converted to Typescript. Typescript consumers will now get static type safety. Flow types are no longer provided.
** getTokens props changes ** When defining the value function passed into a ThemeProvider, the
getTokens parameter cannot be called without props; if no props are provided an empty object {}
must be passed in:
<CustomTheme.Provider
value={t => ({ ...t(), backgroundColor: '#333'})}
>
becomes:
<CustomTheme.Provider
value={t => ({ ...t({}), backgroundColor: '#333'})}
>
** Color palette changes ** Color palettes have been moved into their own file. Users will need to update imports from this:
import { colors } from '@atlaskit/theme';
colors.colorPalette('8');
to this:
import { colorPalette } from '@atlaskit/theme';
colorPalette.colorPalette('8');
or for multi entry-point users:
import * as colors from '@atlaskit/theme/colors';
colors.colorPalette('8');
to this:
import * as colorPalettes from '@atlaskit/theme/color-palette';
colorPalettes.colorPalette('8');
[patch]35d2229b2a:
Adding missing license to packages and update to Copyright 2019 Atlassian Pty Ltd.
[patch]a2d0043716:
Updated version of analytics-next to fix potential incompatibilities with TS 3.6
[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]39c83bb527:
@atlaskit/progress-indicator 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]9f8ab1084b:
Consume analytics-next ts type definitions as an ambient declaration.
[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.