Section message

d82e6f76528ab, (opens new window) - Add direct subpath package exports as part of the linking-platform, search, media, and design-system barrel-removal (de-barrel) migration.

These packages now expose their individual modules via explicit package.json exports subpaths so that consumers can import directly from the leaf module (e.g. @atlaskit/pkg/thing) instead of the package barrel/index. This adds new public entry points without changing or removing any existing exports, so it is a backwards-compatible additive change.

No runtime behaviour changes; this is an API-surface (entry-point) addition to support tree-shaking and to unblock removal of the barrel index files.

48e7d03469b80, (opens new window) - Apply Volt entry-point and barrel-removal standards across these design-system packages. Public exports now resolve directly to ./src/* implementations instead of intermediate ./src/entry-points/* re-exports, root barrels and remaining entry-point shims are marked deprecated in favour of per-export subpaths, and a few new subpaths are added (@atlaskit/badge/badge-new, @atlaskit/tile/tile-skeleton, @atlaskit/popper/main, @atlaskit/section-message/message, @atlaskit/section-message/message-action).

Subpaths and the package root can now resolve to the same module instance. Consumers that deep-imported entry-points/*, or jest.mock()'d a specific subpath may need updates. @atlaskit/image's root export now points at ./src/ui/image/index.tsx. @atlaskit/checkbox/checkbox now exports a named Checkbox from the implementation module (default export retained for backwards compatibility).

Prefer published subpaths over the package root:

If you imported through internal entry-point modules, switch to the public subpath:

cd097a2111788, (opens new window) - Republish packages depending on @atlaskit/react-compiler-gating so their published dependency reference is updated to the renamed @atlaskit/react-compiler-gating scope.

The earlier rename of @atlassian/react-compiler-gating to @atlaskit/react-compiler-gating only bumped the renamed package itself, so dependent packages were never republished and their published versions still referenced the old @atlassian/react-compiler-gating name, which is not available in the public npm registry. This minor bump republishes all affected packages with the corrected dependency.

f2dc9097319f0, (opens new window) - ### Dropped support for legacy Typescript 4 types. Typescript 5 is now the new minimum.

Removes the typesVersions property and dist/types-ts4.5 directory from the dist.

Types are now exclusively via the "types": "dist/types/index.d.ts" property.

• Actions that do not have linkComponent component overrides will no longer utilize the legacy Button component, and now utilize either the Pressable primitive or Link component depending on whether onClick or href props are set. The linkComponent prop otherwise behaves as it did before, but remains deprecated and scheduled to be removed in a later version.
• Plain-text actions with a onClick or href now have body font styles applied by default.

#117363, (opens new window) 10a0f7f6c2027, (opens new window) - 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, (opens new window)

#116552, (opens new window) e002c7033f5f3, (opens new window) - 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/section-message, 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, (opens new window).

#127511, (opens new window) db30e29344013, (opens new window) - 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.

#21570, (opens new window) 89a1b9b02d9, (opens new window) - [ux] - Actions will now wrap onto new lines rather than overflowing the edges, in cases where the actions are wider than the available width of the Section Message.

• Added test ID data attribute to actions list for testing purposes, using the existing testId prop.

edafa2f6366, (opens new window) - [ux]

• Prevent long text overflowing the Section Message content box by utilising CSS property word-break: break-word to add line breaks. This applies to both the title and children props.
• Allow text truncation to work inside Section Message content area by adding overflow: hidden to the flex container. This is due to a quirk with how this property works within CSS flexbox.
• Added test ID data attribute to content container for testing purposes, using the existing testId prop.

Updated dependencies

#13302, (opens new window) cd62b457ff9, (opens new window) - Instrumented Section Message 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.

#10569, (opens new window) 5b0461cc42d, (opens new window) - [ux] In this version we made SectionMessage dramatically faster and lighter

• General performance improvements

• We are now exporting a new component and few new types. The new component is SectionMessageAction, which you can use with the actions props. New types are SectionMessageProps and SectionMessageActionProps.

• BREAKING The actions prop now accepts either a single JSX element, or an array with JSX elements.

• BREAKING linkComponent prop is now moved to SectionMessageAction.

• BREAKING The values for the appearance prop have changed:

  • info is now information
  • confirmation is now success
  • change is now discovery

Running the codemod cli

To run the codemod: You first need to have the latest version installed

Once upgraded, use @atlaskit/codemod-cli via npx:

The CLI will show a list of components and versions so select @atlaskit/section-message@^6.0.0 and you will automatically be upgraded.

What will be changed:

• It will convert the actions prop from an array of objects to an array of SectionMessageAction.
• It will move linkComponent prop from SectionMessage to SectionMessageAction.
• It will update the appearance prop values.

If your usage of SectionMessage cannot be upgraded a comment will be left that a manual change is required.

Run npx @atlaskit/codemod-cli -h for more details on usage.

For Atlassians,

refer to the documentation, (opens new window) for more details on the codemod CLI.

• Converted all the components from class to functional. This improved performance quite a bit. Initial rendering, hydration and re-rendering all have been improved.
• Stopped exporting unused theme variable.
• Added ref support which points to the top level element. Earlier it was not officially supported.
• Dev changes includes: folder restructuring and cleanup, memoizing components, adding techstack in package.json, moving to declarative entry points, removing deprecated version.json etc.

#3885, (opens new window) 6c525a8229, (opens new window) - 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.

• @atlaskit/docs@8.4.0
• @atlaskit/icon@20.1.0
• @atlaskit/webdriver-runner@0.3.0
• @atlaskit/field-range@8.0.2
• @atlaskit/button@13.3.9

• @atlaskit/webdriver-runner@0.2.0
• @atlaskit/button@13.3.8

[patch]6548261c9a, (opens new window):

Remove namespace imports from React, ReactDom, and PropTypes- Updated dependencies 6548261c9a, (opens new window):

• @atlaskit/docs@8.3.2
• @atlaskit/visual-regression@0.1.9
• @atlaskit/button@13.3.7
• @atlaskit/code@11.1.3
• @atlaskit/field-range@8.0.1
• @atlaskit/icon@20.0.1
• @atlaskit/theme@9.5.1

• @atlaskit/field-range@8.0.0
• @atlaskit/icon@20.0.0
• @atlaskit/docs@8.3.1
• @atlaskit/button@13.3.6

[patch]4a223473c5, (opens new window):

Removes babel/runtime from dependencies. Users should see a smaller bundlesize as a result- Updated dependencies 28f8f0e089, (opens new window):

Updated dependencies 82747f2922, (opens new window):

Updated dependencies 4a223473c5, (opens new window):

• @atlaskit/icon@19.1.0
• @atlaskit/theme@9.5.0
• @atlaskit/button@13.3.5
• @atlaskit/code@11.1.1

[patch]d222c2b987, (opens new window):

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:

becomes:

** Color palette changes ** Color palettes have been moved into their own file. Users will need to update imports from this:

to this:

or for multi entry-point users:

to this:

[patch]35d2229b2a, (opens new window):

Adding missing license to packages and update to Copyright 2019 Atlassian Pty Ltd.

[minor]e6439fa292, (opens new window):

Adding an optional prop testId that will set the attribute value data-testid. It will help products to write better integration and end to end tests.

[patch]097b696613, (opens new window):

Components now depend on TS 3.6 internally, in order to fix an issue with TS resolving non-relative imports as relative imports

[patch]ecca4d1dbb, (opens new window):

Upgraded Typescript to 3.3.x

[patch]708028db86, (opens new window):

Change all the imports to theme in Core to use multi entry points

[patch]de35ce8c67, (opens new window):

Updates component maintainers

[patch]bbff8a7d87, (opens new window):

Fixes bug, missing version.json file

[patch]18dfac7332, (opens new window):

In this PR, we are:

• Re-introducing dist build folders
• Adding back cjs
• Replacing es5 by cjs and es2015 by esm
• Creating folders at the root for entry-points
• Removing the generation of the entry-points at the root Please see this ticket, (opens new window) or this page, (opens new window) for further details

[patch]29a1f158c1, (opens new window):

Use default react import in typescript files.

• @atlaskit/docs@8.1.3
• @atlaskit/button@13.0.9
• @atlaskit/icon@19.0.0

[patch]4615439434, (opens new window):

index.ts will now be ignored when publishing to npm

[patch]93bcf314c6, (opens new window):

Added missing tslib dep

• @atlaskit/docs@8.1.2
• @atlaskit/button@13.0.8
• @atlaskit/field-range@7.0.4
• @atlaskit/icon@18.0.0

• @atlaskit/docs@8.1.0
• @atlaskit/field-range@7.0.2
• @atlaskit/code@11.0.0

• @atlaskit/section-message has been converted to Typescript. Typescript consumers will now get static type safety. Flow types are no longer provided. No API or behavioural changes.

• Updates react and react-dom peer dependencies to react@^16.8.0 and react-dom@^16.8.0. To use this package, please ensure you use at least this version of react and react-dom.

• Section message content area now takes 100% of its parent width

• @atlaskit/docs@7.0.3
• @atlaskit/button@12.0.3
• @atlaskit/field-range@6.0.4
• @atlaskit/icon@16.0.9
• @atlaskit/theme@8.1.7

• @atlaskit/docs@7.0.2
• @atlaskit/icon@16.0.8
• @atlaskit/theme@8.1.6
• @atlaskit/field-range@6.0.3
• @atlaskit/button@12.0.0

• @atlaskit/docs@7.0.1
• @atlaskit/icon@16.0.5
• @atlaskit/theme@8.0.1
• @atlaskit/field-range@6.0.1
• @atlaskit/button@11.0.0

[major]76299208e6, (opens new window):

• Drop ES5 from all the flow modules

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:

Previously this was sort of possible for consumers by doing something like:

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, (opens new window) (for external) if you have any questions or queries about this.

• Actions now require a key prop and action text now accepts React Nodes

• Actions will now accept a key prop

• Fixed alignment of the separator dots

• @atlaskit/docs@6.0.1
• @atlaskit/button@10.1.2
• @atlaskit/field-range@5.0.14
• @atlaskit/icon@16.0.0

• Update css styles to display: flex for Actions and replace the content by a mid-dot without escape characters

• @atlaskit/button@10.1.1
• @atlaskit/field-range@5.0.12
• @atlaskit/icon@15.0.2
• @atlaskit/theme@7.0.1
• @atlaskit/docs@6.0.0

• @atlaskit/docs@5.2.3
• @atlaskit/button@10.0.4
• @atlaskit/field-range@5.0.11
• @atlaskit/icon@15.0.1
• @atlaskit/theme@7.0.0

• @atlaskit/docs@5.2.2
• @atlaskit/button@10.0.1
• @atlaskit/icon@15.0.0

• @atlaskit/docs@5.2.1
• @atlaskit/icon@14.6.1
• @atlaskit/theme@6.2.1
• @atlaskit/field-range@5.0.9
• @atlaskit/button@10.0.0

• @atlaskit/docs@5.0.8
• @atlaskit/button@9.0.13
• @atlaskit/icon@14.0.0

• @atlaskit/theme@6.0.0
• @atlaskit/icon@13.2.5
• @atlaskit/field-range@5.0.4
• @atlaskit/button@9.0.6
• @atlaskit/docs@5.0.6

• @atlaskit/button@9.0.5
• @atlaskit/theme@5.1.3
• @atlaskit/field-range@5.0.3
• @atlaskit/icon@13.2.4

• @atlaskit/icon@13.2.2
• @atlaskit/button@9.0.4
• @atlaskit/theme@5.1.2
• @atlaskit/field-range@5.0.2
• @atlaskit/docs@5.0.2

• @atlaskit/button@9.0.3
• @atlaskit/theme@5.1.1
• @atlaskit/field-range@5.0.1
• @atlaskit/icon@13.2.1

• @atlaskit/button@9.0.0
• @atlaskit/theme@5.0.0
• @atlaskit/field-range@5.0.0
• @atlaskit/docs@5.0.0
• @atlaskit/icon@13.0.0

• @atlaskit/button@9.0.0
• @atlaskit/theme@5.0.0
• @atlaskit/field-range@5.0.0
• @atlaskit/docs@5.0.0
• @atlaskit/icon@13.0.0