Radio

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.

f0bf5f838abd5, (opens new window) - Apply Volt entry-point and barrel-removal standards across these packages. Public exports now resolve directly to ./src/* implementations instead of intermediate ./src/entry-points/* re-exports.

Prefer published subpaths over the package root or internal entry-point paths:

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.

#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)

#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.

#13302, (opens new window) f276913fa2c, (opens new window) - Instrumented Radio 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.

#4749, (opens new window) 44ef6437cd, (opens new window) - In this version, we made radio dramatically faster and lighter 😍

In 5.0.0 we improved the performance of radio by making it more similar to a native radio input.

• Previously we rendered a hidden input and an svg for the radio icon. This way we could get all the accessibility benefits of using a native radio input while being able to style the svg. We now use appearance: none on the input, enabling us to style the input and the after pseudo-element. This removes the need for an svg.
• Previously all interaction styles were generated in JS using events, causing unnecessary and slow rerenders. Now all styles for the radio are applied using css selectors.
• Because the input is now visible, we have changed the test id from ${testId}--hidden-radio to ${testId}--radio-input to provide less usage friction. We looked into product usage of the testId and we have reached out to the owners of any code that would be effected (there was only one).
• Dropped the peerDependency on styled-components@3 in favour of using @emotion/core.
• Converted to function components.
• Added the ability to forward a ref to a radio input.
• Remove the RadioIcon export, you should just use the Radio without a label if you want this functionality.
• Restricted types for Radio and RadioGroup. RadioGroup previously allowed you to pass any props so this has been restricted to only those used. The isChecked prop in theoptions prop for RadioGroup has been removed. You can only set a Radio as checked if the value of the Radio is the selected value in the RadioGroup. Radio used to explicitly define input attributes as props and now it extends InputHTMLAttributes allowing you to pass any input attribute as a prop.
• There was a bug where all onMouse events were passed onto both the input element and the Radio, which means they would be called multiple times. Now they are only passed to the input element.
• As Radio acts as a native radio input, the name prop on each RadioGroup needs to be unique or each RadioGroup with the same name needs to be inside a form element. This is because the name attribute on radio inputs is used to link the inputs so if you have two separate RadioGroup's with the same name, the browser views them as one radio group.

#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.

[minor]f0af33ead6, (opens new window):

Add name prop to RadioGroup

• @atlaskit/form@7.2.0
• @atlaskit/build-utils@2.6.4
• @atlaskit/docs@8.5.0

• @atlaskit/docs@8.4.0
• @atlaskit/icon@20.1.0
• @atlaskit/webdriver-runner@0.3.0
• @atlaskit/button@13.3.9
• @atlaskit/checkbox@10.1.10
• @atlaskit/form@7.1.5

• @atlaskit/webdriver-runner@0.2.0
• @atlaskit/button@13.3.8
• @atlaskit/checkbox@10.1.9
• @atlaskit/form@7.1.4

[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/analytics-next@6.3.5
• @atlaskit/button@13.3.7
• @atlaskit/checkbox@10.1.7
• @atlaskit/form@7.1.2
• @atlaskit/icon@20.0.1
• @atlaskit/theme@9.5.1

• @atlaskit/icon@20.0.0
• @atlaskit/form@7.1.1
• @atlaskit/docs@8.3.1
• @atlaskit/button@13.3.6
• @atlaskit/checkbox@10.1.6

[patch]e20d7996ca, (opens new window):

Fixes radio value from string | number to just string to match the current implementation.- Updated dependencies ec76622d34, (opens new window):

Updated dependencies d93de8e56e, (opens new window):

• @atlaskit/form@7.0.1

[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):

Updated dependencies 6a8bc6f866, (opens new window):

• @atlaskit/icon@19.1.0
• @atlaskit/theme@9.5.0
• @atlaskit/button@13.3.5
• @atlaskit/checkbox@10.1.5

[patch]24865cfaff, (opens new window):

Form has been converted to Typescript. TypeScript consumers will now get static type safety. Flow types are no longer provided. No API changes.- Updated dependencies 24865cfaff, (opens new window):

Updated dependencies 24865cfaff, (opens new window):

Updated dependencies 24865cfaff, (opens new window):

Updated dependencies 24865cfaff, (opens new window):

Updated dependencies 24865cfaff, (opens new window):

• @atlaskit/analytics-next@6.3.3
• @atlaskit/form@7.0.0
• @atlaskit/checkbox@10.1.4

[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]70e57645f2, (opens new window):

Updates controlled example to show better pattern for state duplication between RadioGroup and Form

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

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

[patch]a2d0043716, (opens new window):

Updated version of analytics-next to fix potential incompatibilities with TS 3.6

[minor]ff521a0e20, (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.

• @atlaskit/button@13.3.1
• @atlaskit/form@6.2.3
• @atlaskit/checkbox@10.0.0
• @atlaskit/docs@8.1.7

[patch]7dc767eabb, (opens new window):

onChange is now marked as an optional prop

[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]926b43142b, (opens new window):

Analytics-next has been converted to Typescript. Typescript consumers will now get static type safety. Flow types are no longer provided. No behavioural changes.

Breaking changes

• withAnalyticsForSumTypeProps alias has been removed, please use withAnalyticsEvents
• AnalyticsContextWrappedComp alias has been removed, please use withAnalyticsContext

Breaking changes to TypeScript annotations

• withAnalyticsEvents now infers proptypes automatically, consumers no longer need to provide props as a generic type.
• withAnalyticsContext now infers proptypes automatically, consumers no longer need to provide props as a generic type.
• Type WithAnalyticsEventProps has been renamed to WithAnalyticsEventsProps to match source code
• Type CreateUIAnalyticsEventSignature has been renamed to CreateUIAnalyticsEvent to match source code
• Type UIAnalyticsEventHandlerSignature has been renamed to UIAnalyticsEventHandler to match source code
• Type AnalyticsEventsPayload has been renamed to AnalyticsEventPayload
• Type ObjectType has been removed, please use Record<string, any> or [key: string]: any
• Type UIAnalyticsEventInterface has been removed, please use UIAnalyticsEvent
• Type AnalyticsEventInterface has been removed, please use AnalyticsEvent
• Type CreateAndFireEventFunction removed and should now be inferred by TypeScript
• Type AnalyticsEventUpdater removed and should now be inferred by TypeScript

[patch]9f8ab1084b, (opens new window):

Consume analytics-next ts type definitions as an ambient declaration.

[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]d0db01b410, (opens new window):

TypeScript users of withAnalyticsEvents and withAnalyticsContext are now required to provide props as a generic type. This is so that TypeScript can correctly calculate the props and defaultProps of the returned component.

Before:

After:

• @atlaskit/button@13.0.10
• @atlaskit/form@6.1.2
• @atlaskit/checkbox@9.0.0

• @atlaskit/docs@8.1.3
• @atlaskit/button@13.0.9
• @atlaskit/checkbox@8.0.5
• @atlaskit/form@6.1.1
• @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/checkbox@8.0.2
• @atlaskit/form@6.0.5
• @atlaskit/icon@18.0.0

• @atlaskit/button@13.0.6
• @atlaskit/form@6.0.4
• @atlaskit/checkbox@8.0.0
• @atlaskit/icon@17.2.0
• @atlaskit/theme@9.1.0

• This is just a safety release in case anything strange happened in in the previous one. See Pull Request #5942 for details

• @atlaskit/radio 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.

• This major release indicates that this package is no longer under dev preview but is ready for use

• @atlaskit/docs@7.0.3
• @atlaskit/button@12.0.3
• @atlaskit/checkbox@6.0.4
• @atlaskit/form@5.2.7
• @atlaskit/icon@16.0.9
• @atlaskit/section-message@2.0.3
• @atlaskit/theme@8.1.7

• @atlaskit/docs@7.0.2
• @atlaskit/analytics-next@4.0.3
• @atlaskit/checkbox@6.0.3
• @atlaskit/form@5.2.5
• @atlaskit/icon@16.0.8
• @atlaskit/section-message@2.0.2
• @atlaskit/theme@8.1.6
• @atlaskit/button@12.0.0

• @atlaskit/docs@7.0.1
• @atlaskit/analytics-next@4.0.1
• @atlaskit/checkbox@6.0.1
• @atlaskit/form@5.2.1
• @atlaskit/icon@16.0.5
• @atlaskit/section-message@2.0.1
• @atlaskit/theme@8.0.1
• @atlaskit/button@11.0.0

[minor]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.

• Added test to make sure props are passed hidden input

• @atlaskit/docs@6.0.1
• @atlaskit/button@10.1.2
• @atlaskit/checkbox@5.0.11
• @atlaskit/form@5.1.2
• @atlaskit/section-message@1.0.16
• @atlaskit/icon@16.0.0

[patch]a048a85, (opens new window):

• Updated to be compatible with new Forms API

Updated dependencies 647a46f, (opens new window):

• @atlaskit/form@5.0.0

• @atlaskit/analytics-next@3.1.2
• @atlaskit/button@10.1.1
• @atlaskit/checkbox@5.0.9
• @atlaskit/form@4.0.21
• @atlaskit/icon@15.0.2
• @atlaskit/section-message@1.0.14
• @atlaskit/theme@7.0.1
• @atlaskit/docs@6.0.0

• @atlaskit/docs@5.2.3
• @atlaskit/button@10.0.4
• @atlaskit/field-base@11.0.12
• @atlaskit/form@4.0.20
• @atlaskit/icon@15.0.1
• @atlaskit/section-message@1.0.13
• @atlaskit/theme@7.0.0

• @atlaskit/docs@5.2.2
• @atlaskit/button@10.0.1
• @atlaskit/field-base@11.0.11
• @atlaskit/form@4.0.19
• @atlaskit/section-message@1.0.12
• @atlaskit/icon@15.0.0

• @atlaskit/docs@5.2.1
• @atlaskit/analytics-next@3.1.1
• @atlaskit/form@4.0.18
• @atlaskit/icon@14.6.1
• @atlaskit/section-message@1.0.11
• @atlaskit/theme@6.2.1
• @atlaskit/button@10.0.0

• Add isDisabled prop to RadioGroup, once set will set the isDisabled value for all Radio elements within the group

• BREAKING: defaultCheckedValue and checkedValue props in the RadioGroup component now changed to defaultValue and value respectively

• @atlaskit/docs@5.0.8
• @atlaskit/button@9.0.13
• @atlaskit/field-base@11.0.8
• @atlaskit/form@4.0.10
• @atlaskit/section-message@1.0.8
• @atlaskit/icon@14.0.0