@atlaskit/navigation-system 7.2.1 → 8.0.0

package/dist/es2019/ui/page-layout/side-nav/element-context.js

@@ -1,21 +0,0 @@
-import React, { createContext, useContext, useRef } from 'react';
-const SideNavRefContext = /*#__PURE__*/createContext({
-  current: null
-});
-export function SideNavElementProvider({
-  children
-}) {
-  const sideNavRef = useRef(null);
-  return /*#__PURE__*/React.createElement(SideNavRefContext.Provider, {
-    value: sideNavRef
-  }, children);
-}
-
-/**
- * Returns a ref for the side navigation that is accessible to other Page Layout slots.
- *
- * Used by the Panel to measure the SideNav when it is calculating its resize bounds.
- */
-export function useSideNavRef() {
-  return useContext(SideNavRefContext);
-}

package/dist/es2019/ui/page-layout/side-nav/toggle-button-context.js

@@ -1,19 +0,0 @@
-import { createContext } from 'react';
-import __noop from '@atlaskit/ds-lib/noop';
-/**
- * Context for the side nav toggle button element.
- * Used to power the side nav flyout by allowing the side nav to bind event listeners to the button element.
- */
-export const SideNavToggleButtonElement = /*#__PURE__*/createContext(null);
-
-/**
- * Context for the callback ref used to respond to toggle button ref being attached. It is used to update the
- * `SideNavToggleButtonRef` state so consumers can react to the ref being attached.
- *
- * e.g. Once the side nav toggle button has been mounted, the side nav can bind mouse event listeners to it
- * to power the sidenav flyout.
- *
- * A callback ref is needed because the side nav can be mounted before the elements in the top bar (e.g. if the element
- *  is lazy loaded, which happens in Jira and Confluence), which would prevent the event listeners from being set up.
- */
-export const SideNavToggleButtonAttachRef = /*#__PURE__*/createContext(__noop);

package/dist/es2019/ui/top-nav-items/themed/migration.js

@@ -1,45 +0,0 @@
-import _extends from "@babel/runtime/helpers/extends";
-import React, { forwardRef } from 'react';
-import AkButton, { IconButton as AkIconButton, LinkButton as AkLinkButton, LinkIconButton as AkLinkIconButton } from '@atlaskit/button/new';
-import { ThemedButton, ThemedIconButton, ThemedLinkButton, ThemedLinkIconButton } from './button';
-import { useHasCustomTheme } from './has-custom-theme-context';
-// Explicitly typed to use only the themed button API,
-// which is a subset of the normal button API
-const IconButton = /*#__PURE__*/forwardRef((props, ref) => {
-  const hasCustomTheme = useHasCustomTheme();
-  const Component = hasCustomTheme ? ThemedIconButton : AkIconButton;
-  return /*#__PURE__*/React.createElement(Component, _extends({
-    ref: ref
-  }, props));
-});
-
-// Explicitly typed to use only the themed button API,
-// which is a subset of the normal button API
-const LinkIconButton = /*#__PURE__*/forwardRef((props, ref) => {
-  const hasCustomTheme = useHasCustomTheme();
-  const Component = hasCustomTheme ? ThemedLinkIconButton : AkLinkIconButton;
-  return /*#__PURE__*/React.createElement(Component, _extends({
-    ref: ref
-  }, props));
-});
-
-// Explicitly typed to use only the themed button API,
-// which is a subset of the normal button API
-const Button = /*#__PURE__*/forwardRef((props, ref) => {
-  const hasCustomTheme = useHasCustomTheme();
-  const Component = hasCustomTheme ? ThemedButton : AkButton;
-  return /*#__PURE__*/React.createElement(Component, _extends({
-    ref: ref
-  }, props));
-});
-
-// Explicitly typed to use only the themed button API,
-// which is a subset of the normal button API
-const LinkButton = /*#__PURE__*/forwardRef((props, ref) => {
-  const hasCustomTheme = useHasCustomTheme();
-  const Component = hasCustomTheme ? ThemedLinkButton : AkLinkButton;
-  return /*#__PURE__*/React.createElement(Component, _extends({
-    ref: ref
-  }, props));
-});
-export { IconButton, Button, LinkIconButton, LinkButton };

package/dist/esm/context/top-nav-start/top-nav-start-context.js

@@ -1,20 +0,0 @@
-import { createContext } from 'react';
-import __noop from '@atlaskit/ds-lib/noop';
-
-/**
- * Context for the TopNavStart container element
- * Used to power the side nav flyout by allowing the side nav to bind event listeners to the element, so we can
- * keep the flyout open while the user mouses from the top bar to the side nav.
- */
-export var TopNavStartElement = /*#__PURE__*/createContext(null);
-
-/**
- * Context for the callback ref used to respond to the TopNavStart element ref being attached. It is used to update the
- * `TopNavStartElement` state so consumers can react to the ref being attached.
- *
- * e.g. Once the TopNavStart element has been mounted, the side nav can bind mouse event listeners to it.
- *
- * A callback ref is needed because the side nav can be mounted before elements in the top bar (e.g. if the element is lazy loaded),
- * which happens in Jira and Confluence), which would prevent the event listeners from being set up.
- */
-export var TopNavStartAttachRef = /*#__PURE__*/createContext(__noop);

package/dist/esm/ui/page-layout/hoist-utils.js

@@ -1,51 +0,0 @@
-import React from 'react';
-import { gridRootId } from './root';
-
-/**
- * This is not ideal and shouldn't be used by anything outside of `<Banner>` and `<TopNav>`.
- *
- * This makes the other page layout elements aware that the banner and top bar have been mounted, provides them
- * with their heights. This is needed to power the stick points of page layout elements like SideNav and Panel.
- *
- * We should clean this up once we have a better solution, such as moving the size props for banner and top bar into `Root`.
- */
-export var HoistCssVarToLocalGrid = function HoistCssVarToLocalGrid(_ref) {
-  var variableName = _ref.variableName,
-    value = _ref.value;
-  return /*#__PURE__*/React.createElement("style", null, "#".concat(gridRootId, " { ").concat(variableName, ": ").concat(value, "px }"));
-};
-var getCssStringValue = function getCssStringValue(value) {
-  return typeof value === 'number' ? "".concat(value, "px") : value;
-};
-
-/**
- * Hoists CSS variables to the document root. This is support the legacy edge case of monolith pages being injected as a
- * sibling to the page layout, as opposed to within the `Main` slot.
- */
-export var DangerouslyHoistCssVarToDocumentRoot = function DangerouslyHoistCssVarToDocumentRoot(_ref2) {
-  var variableName = _ref2.variableName,
-    value = _ref2.value,
-    mediaQuery = _ref2.mediaQuery,
-    responsiveValue = _ref2.responsiveValue;
-  /**
-   * Note don't put multiple variables in multiple lines. eg
-   * <style>
-   *   {css1}
-   *   {css2}
-   * </style>
-   *
-   * React will insert an empty HTML comment in between the text in SSR.
-   * This is not a valid tag and will break the page.
-   * <style>foo<!-- -->bar</style>
-   */
-  var style = ":root { ".concat(variableName, ": ").concat(getCssStringValue(value), " }");
-  if (mediaQuery && responsiveValue) {
-    style += " ".concat(mediaQuery, " { :root { ").concat(variableName, ": ").concat(getCssStringValue(responsiveValue), " } }");
-  }
-  return (
-    /*#__PURE__*/
-    // Using a global style is required for SSR, as we can't use React hooks
-    // eslint-disable-next-line @atlaskit/ui-styling-standard/no-global-styles
-    React.createElement("style", null, style)
-  );
-};

package/dist/esm/ui/page-layout/side-nav/element-context.js

@@ -1,20 +0,0 @@
-import React, { createContext, useContext, useRef } from 'react';
-var SideNavRefContext = /*#__PURE__*/createContext({
-  current: null
-});
-export function SideNavElementProvider(_ref) {
-  var children = _ref.children;
-  var sideNavRef = useRef(null);
-  return /*#__PURE__*/React.createElement(SideNavRefContext.Provider, {
-    value: sideNavRef
-  }, children);
-}
-
-/**
- * Returns a ref for the side navigation that is accessible to other Page Layout slots.
- *
- * Used by the Panel to measure the SideNav when it is calculating its resize bounds.
- */
-export function useSideNavRef() {
-  return useContext(SideNavRefContext);
-}

package/dist/esm/ui/page-layout/side-nav/toggle-button-context.js

@@ -1,19 +0,0 @@
-import { createContext } from 'react';
-import __noop from '@atlaskit/ds-lib/noop';
-/**
- * Context for the side nav toggle button element.
- * Used to power the side nav flyout by allowing the side nav to bind event listeners to the button element.
- */
-export var SideNavToggleButtonElement = /*#__PURE__*/createContext(null);
-
-/**
- * Context for the callback ref used to respond to toggle button ref being attached. It is used to update the
- * `SideNavToggleButtonRef` state so consumers can react to the ref being attached.
- *
- * e.g. Once the side nav toggle button has been mounted, the side nav can bind mouse event listeners to it
- * to power the sidenav flyout.
- *
- * A callback ref is needed because the side nav can be mounted before the elements in the top bar (e.g. if the element
- *  is lazy loaded, which happens in Jira and Confluence), which would prevent the event listeners from being set up.
- */
-export var SideNavToggleButtonAttachRef = /*#__PURE__*/createContext(__noop);

package/dist/esm/ui/top-nav-items/themed/migration.js

@@ -1,45 +0,0 @@
-import _extends from "@babel/runtime/helpers/extends";
-import React, { forwardRef } from 'react';
-import AkButton, { IconButton as AkIconButton, LinkButton as AkLinkButton, LinkIconButton as AkLinkIconButton } from '@atlaskit/button/new';
-import { ThemedButton, ThemedIconButton, ThemedLinkButton, ThemedLinkIconButton } from './button';
-import { useHasCustomTheme } from './has-custom-theme-context';
-// Explicitly typed to use only the themed button API,
-// which is a subset of the normal button API
-var IconButton = /*#__PURE__*/forwardRef(function (props, ref) {
-  var hasCustomTheme = useHasCustomTheme();
-  var Component = hasCustomTheme ? ThemedIconButton : AkIconButton;
-  return /*#__PURE__*/React.createElement(Component, _extends({
-    ref: ref
-  }, props));
-});
-
-// Explicitly typed to use only the themed button API,
-// which is a subset of the normal button API
-var LinkIconButton = /*#__PURE__*/forwardRef(function (props, ref) {
-  var hasCustomTheme = useHasCustomTheme();
-  var Component = hasCustomTheme ? ThemedLinkIconButton : AkLinkIconButton;
-  return /*#__PURE__*/React.createElement(Component, _extends({
-    ref: ref
-  }, props));
-});
-
-// Explicitly typed to use only the themed button API,
-// which is a subset of the normal button API
-var Button = /*#__PURE__*/forwardRef(function (props, ref) {
-  var hasCustomTheme = useHasCustomTheme();
-  var Component = hasCustomTheme ? ThemedButton : AkButton;
-  return /*#__PURE__*/React.createElement(Component, _extends({
-    ref: ref
-  }, props));
-});
-
-// Explicitly typed to use only the themed button API,
-// which is a subset of the normal button API
-var LinkButton = /*#__PURE__*/forwardRef(function (props, ref) {
-  var hasCustomTheme = useHasCustomTheme();
-  var Component = hasCustomTheme ? ThemedLinkButton : AkLinkButton;
-  return /*#__PURE__*/React.createElement(Component, _extends({
-    ref: ref
-  }, props));
-});
-export { IconButton, Button, LinkIconButton, LinkButton };

package/dist/types/context/top-nav-start/top-nav-start-context.d.ts

@@ -1,16 +0,0 @@
-/**
- * Context for the TopNavStart container element
- * Used to power the side nav flyout by allowing the side nav to bind event listeners to the element, so we can
- * keep the flyout open while the user mouses from the top bar to the side nav.
- */
-export declare const TopNavStartElement: import('react').Context<HTMLDivElement | null>;
-/**
- * Context for the callback ref used to respond to the TopNavStart element ref being attached. It is used to update the
- * `TopNavStartElement` state so consumers can react to the ref being attached.
- *
- * e.g. Once the TopNavStart element has been mounted, the side nav can bind mouse event listeners to it.
- *
- * A callback ref is needed because the side nav can be mounted before elements in the top bar (e.g. if the element is lazy loaded),
- * which happens in Jira and Confluence), which would prevent the event listeners from being set up.
- */
-export declare const TopNavStartAttachRef: import('react').Context<(newVal: HTMLDivElement | null) => void>;

package/dist/types/ui/page-layout/panel-splitter/get-width.d.ts

@@ -1,16 +0,0 @@
-import type { DragLocationHistory } from '@atlaskit/pragmatic-drag-and-drop/types';
-/**
- * ⚠️ Note: We are using the initial client location captured from the mousedown event, not from the dragstart event.
- * Some browser extensions can cause the client locations (e.g. clientX) in the `dragstart` event to incorrectly return 0.
- */
-export declare const getWidthFromDragLocation: ({ initialWidth, location, initialClientX, direction, position, }: {
-    initialWidth: number;
-    location: DragLocationHistory;
-    initialClientX: number;
-    direction: "ltr" | "rtl";
-    position: "start" | "end";
-}) => number;
-/**
- * Returns the computed width of an element in pixels.
- */
-export declare const getPixelWidth: (element: HTMLElement) => number;

package/dist/types/ui/page-layout/side-nav/toggle-button-context.d.ts

@@ -1,16 +0,0 @@
-/**
- * Context for the side nav toggle button element.
- * Used to power the side nav flyout by allowing the side nav to bind event listeners to the button element.
- */
-export declare const SideNavToggleButtonElement: import('react').Context<HTMLButtonElement | null>;
-/**
- * Context for the callback ref used to respond to toggle button ref being attached. It is used to update the
- * `SideNavToggleButtonRef` state so consumers can react to the ref being attached.
- *
- * e.g. Once the side nav toggle button has been mounted, the side nav can bind mouse event listeners to it
- * to power the sidenav flyout.
- *
- * A callback ref is needed because the side nav can be mounted before the elements in the top bar (e.g. if the element
- *  is lazy loaded, which happens in Jira and Confluence), which would prevent the event listeners from being set up.
- */
-export declare const SideNavToggleButtonAttachRef: import('react').Context<(newVal: HTMLButtonElement | null) => void>;

package/dist/types/ui/top-nav-items/themed/migration.d.ts

@@ -1,10 +0,0 @@
-import React from 'react';
-import { type ThemedButtonProps, type ThemedIconButtonProps, type ThemedLinkButtonProps, type ThemedLinkIconButtonProps } from './button';
-type IconButtonMigrationProps = {
-    isTooltipDisabled?: boolean;
-};
-declare const IconButton: React.ForwardRefExoticComponent<React.PropsWithoutRef<ThemedIconButtonProps & IconButtonMigrationProps> & React.RefAttributes<HTMLButtonElement>>;
-declare const LinkIconButton: React.ForwardRefExoticComponent<React.PropsWithoutRef<ThemedLinkIconButtonProps & IconButtonMigrationProps> & React.RefAttributes<HTMLAnchorElement>>;
-declare const Button: React.ForwardRefExoticComponent<React.PropsWithoutRef<ThemedButtonProps & IconButtonMigrationProps> & React.RefAttributes<HTMLButtonElement>>;
-declare const LinkButton: React.ForwardRefExoticComponent<React.PropsWithoutRef<ThemedLinkButtonProps> & React.RefAttributes<HTMLAnchorElement>>;
-export { IconButton, Button, LinkIconButton, LinkButton };

package/dist/types-ts4.5/context/top-nav-start/top-nav-start-context.d.ts

@@ -1,16 +0,0 @@
-/**
- * Context for the TopNavStart container element
- * Used to power the side nav flyout by allowing the side nav to bind event listeners to the element, so we can
- * keep the flyout open while the user mouses from the top bar to the side nav.
- */
-export declare const TopNavStartElement: import('react').Context<HTMLDivElement | null>;
-/**
- * Context for the callback ref used to respond to the TopNavStart element ref being attached. It is used to update the
- * `TopNavStartElement` state so consumers can react to the ref being attached.
- *
- * e.g. Once the TopNavStart element has been mounted, the side nav can bind mouse event listeners to it.
- *
- * A callback ref is needed because the side nav can be mounted before elements in the top bar (e.g. if the element is lazy loaded),
- * which happens in Jira and Confluence), which would prevent the event listeners from being set up.
- */
-export declare const TopNavStartAttachRef: import('react').Context<(newVal: HTMLDivElement | null) => void>;

package/dist/types-ts4.5/ui/page-layout/panel-splitter/get-width.d.ts

@@ -1,16 +0,0 @@
-import type { DragLocationHistory } from '@atlaskit/pragmatic-drag-and-drop/types';
-/**
- * ⚠️ Note: We are using the initial client location captured from the mousedown event, not from the dragstart event.
- * Some browser extensions can cause the client locations (e.g. clientX) in the `dragstart` event to incorrectly return 0.
- */
-export declare const getWidthFromDragLocation: ({ initialWidth, location, initialClientX, direction, position, }: {
-    initialWidth: number;
-    location: DragLocationHistory;
-    initialClientX: number;
-    direction: "ltr" | "rtl";
-    position: "start" | "end";
-}) => number;
-/**
- * Returns the computed width of an element in pixels.
- */
-export declare const getPixelWidth: (element: HTMLElement) => number;

package/dist/types-ts4.5/ui/page-layout/side-nav/toggle-button-context.d.ts

@@ -1,16 +0,0 @@
-/**
- * Context for the side nav toggle button element.
- * Used to power the side nav flyout by allowing the side nav to bind event listeners to the button element.
- */
-export declare const SideNavToggleButtonElement: import('react').Context<HTMLButtonElement | null>;
-/**
- * Context for the callback ref used to respond to toggle button ref being attached. It is used to update the
- * `SideNavToggleButtonRef` state so consumers can react to the ref being attached.
- *
- * e.g. Once the side nav toggle button has been mounted, the side nav can bind mouse event listeners to it
- * to power the sidenav flyout.
- *
- * A callback ref is needed because the side nav can be mounted before the elements in the top bar (e.g. if the element
- *  is lazy loaded, which happens in Jira and Confluence), which would prevent the event listeners from being set up.
- */
-export declare const SideNavToggleButtonAttachRef: import('react').Context<(newVal: HTMLButtonElement | null) => void>;

package/dist/types-ts4.5/ui/top-nav-items/themed/migration.d.ts

@@ -1,10 +0,0 @@
-import React from 'react';
-import { type ThemedButtonProps, type ThemedIconButtonProps, type ThemedLinkButtonProps, type ThemedLinkIconButtonProps } from './button';
-type IconButtonMigrationProps = {
-    isTooltipDisabled?: boolean;
-};
-declare const IconButton: React.ForwardRefExoticComponent<React.PropsWithoutRef<ThemedIconButtonProps & IconButtonMigrationProps> & React.RefAttributes<HTMLButtonElement>>;
-declare const LinkIconButton: React.ForwardRefExoticComponent<React.PropsWithoutRef<ThemedLinkIconButtonProps & IconButtonMigrationProps> & React.RefAttributes<HTMLAnchorElement>>;
-declare const Button: React.ForwardRefExoticComponent<React.PropsWithoutRef<ThemedButtonProps & IconButtonMigrationProps> & React.RefAttributes<HTMLButtonElement>>;
-declare const LinkButton: React.ForwardRefExoticComponent<React.PropsWithoutRef<ThemedLinkButtonProps> & React.RefAttributes<HTMLAnchorElement>>;
-export { IconButton, Button, LinkIconButton, LinkButton };