@braid-design-system/docs-ui@1.1.0

Minor Changes

• Add MenuButton component used to show and hide the navigation sidebar on mobile devices. (#1409)

Patch Changes

• Provide correct types according to https://arethetypeswrong.github.io (#1413)

braid-design-system@32.14.1

Patch Changes

• TooltipRenderer: Fix useLayoutEffect warnings during SSR (#1407)

• Tabs: Improve positioning of the active underline (#1407)

• Fixes a bug where the reset module mistakenly included all the tokens for all the themes. (#1405)

  Additionally, this includes significant compilation improvements to ensure that only styles for the components being used are included — speeding up build times and reducing the overall CSS bundle size.

@braid-design-system/docs-ui@1.0.0

Major Changes

• Create new package named docs-ui. (#1401)

  This package will contain components for building documentation sites with a consistent user experience to the Braid Design System website.

  Currently, this package contains:

  • A single component: LinkableHeading.
  • A README.md for documenting this package and all its components.

Patch Changes

• LinkableHeading: Remove space character between heading and link icon, instead use only margin value. (#1403)

braid-design-system@32.14.0

Minor Changes

• Add optional tooltipPlacement prop to ButtonIcon (#1390)

  The tooltipPlacement prop allows you to specify the placement of the tooltip to either top or bottom.
  The default value is top.

  EXAMPLE USAGE:

  <ButtonIcon tooltipPlacement="bottom" />

braid-design-system@32.13.0

Minor Changes

• seekJobs: Update formAccent colour (#1387)

  The formAccent tone, used through our form fields and buttons, is being updated to a derivative of the SEEK brand blue.

  As this update only relates to the seekJobs theme, consumers of other themes will not be affected.

braid-design-system@32.12.5

Patch Changes

• The Braid Provider contains some code to check that it's running in a browser context (otherwise a BraidTestProvider should be used). (#1382)

  Part of this check was looking to see if there was a navigator object, which was not available in Node.
  If there were, it would check the userAgent to determine if it was inside jsdom.

  Node 21 has a navigator object, but it doesn't have a userAgent property, so this check was failing (cannot read property 'indexOf' of undefined).

  The "are we in JSDom" check in the BraidProvider has now been reworked slightly to account for the potentially existing but empty navigator object.

braid-design-system@32.12.4

Patch Changes

• TextLink, TextLinkButton: Ensure consistent underline thickness on weak links (#1380)

  A subtle bug affecting weak links was resulting in a change in underline thickness on hover.
  This bug has been fixed such that weak links now always have the same underline thickness regardless of hover state.

braid-design-system@32.12.3

Patch Changes

• Fix an arbitrary code execution vulnerability (#1377)

braid-design-system@32.12.2

Patch Changes

• TooltipRenderer: Re-evaluate position when trigger or children changes (#1374)

  Fixes an issue where the tooltip would not re-evaluate its position when the trigger or children prop changed while the tooltip was already open.

@braid-design-system/source.macro@0.1.1

Patch Changes

• Preserve new lines in the output code (#1372)

  Before:

  const responsiveValue = useResponsiveValue();
  const isMobile = responsiveValue({
    mobile: true,
    tablet: false,
  });
  const isDesktopOrAbove = responsiveValue({
    mobile: false,
    desktop: true,
  });

  After:

  const responsiveValue = useResponsiveValue();
  
  const isMobile = responsiveValue({
    mobile: true,
    tablet: false,
  });
  
  const isDesktopOrAbove = responsiveValue({
    mobile: false,
    desktop: true,
  });