@dxc-technology/halstack-react 0.0.0-dfcca07 → 0.0.0-dfd09f9

package/password-input/types.d.ts

@@ -30,25 +30,28 @@ declare type Props = {
      * This function will be called when the user types within the input
      * element of the component. An object including the current value and
      * the error (if the value entered is not valid) will be passed to this
-     * function. If there is no error, error will be null.
+     * function. If there is no error, error will not be defined.
      * */
     onChange?: (val: {
         value: string;
-        error: string | null;
+        error?: string;
     }) => void;
     /**
      * This function will be called when the input element loses the focus.
      * An object including the input value and the error (if the value entered is
-     * not valid) will be passed to this function. If there is no error, error will be null.
+     * not valid) will be passed to this function. If there is no error, error will not be defined.
      */
     onBlur?: (val: {
         value: string;
-        error: string | null;
+        error?: string;
     }) => void;
     /**
-     * If it is defined, the component will change its appearance, showing
-     * the error below the password input component. If it is not defined, the
-     * error messages will be managed internally, but never displayed on its own.
+     * If it is a defined value and also a truthy string, the component will
+     * change its appearance, showing the error below the password input
+     * component. If the defined value is an empty string, it will reserve a
+     * space below the component for a future error, but it would not change
+     * its look. In case of being undefined or null, both the appearance and
+     * the space for the error message would not be modified.
      */
     error?: string;
     /**
@@ -58,7 +61,7 @@ declare type Props = {
      * the pattern, the onBlur and onChange functions will be called with the
      * current value and an internal error informing that this value does not
      * match the pattern. If the pattern is met, the error parameter of both
-     * events will be null.
+     * events will not be defined.
      */
     pattern?: string;
     /**
@@ -68,7 +71,7 @@ declare type Props = {
      * comply the minimum length, the onBlur and onChange functions will be called
      * with the current value and an internal error informing that the value
      * length does not comply the specified range. If a valid length is
-     * reached, the error parameter of both events will be null.
+     * reached, the error parameter of both events will not be defined.
      */
     minLength?: number;
     /**
@@ -78,7 +81,7 @@ declare type Props = {
      * comply the maximum length, the onBlur and onChange functions will be called
      * with the current value and an internal error informing that the value
      * length does not comply the specified range. If a valid length is
-     * reached, the error parameter of both events will be null.
+     * reached, the error parameter of both events will not be defined.
      */
     maxLength?: number;
     /**

package/progress-bar/ProgressBar.js

@@ -21,9 +21,9 @@ var _LinearProgress = _interopRequireDefault(require("@material-ui/core/LinearPr
 
 var _variables = require("../common/variables.js");
 
-var _useTheme = _interopRequireDefault(require("../useTheme.js"));
+var _useTheme = _interopRequireDefault(require("../useTheme"));
 
-var _BackgroundColorContext = _interopRequireDefault(require("../BackgroundColorContext.js"));
+var _BackgroundColorContext = _interopRequireDefault(require("../BackgroundColorContext"));
 
 var _templateObject, _templateObject2, _templateObject3, _templateObject4, _templateObject5, _templateObject6;
 
@@ -59,9 +59,9 @@ var DxcProgressBar = function DxcProgressBar(_ref) {
     overlay: overlay,
     showValue: showValue,
     backgroundType: backgroundType
-  }, value === null ? 0 : value >= 0 && value <= 100 ? value : value < 0 ? 0 : 100, " %")), /*#__PURE__*/_react["default"].createElement(_LinearProgress["default"], {
+  }, value === null || value === undefined ? 0 : value >= 0 && value <= 100 ? value : value < 0 ? 0 : 100, " %")), /*#__PURE__*/_react["default"].createElement(_LinearProgress["default"], {
     variant: showValue ? "determinate" : "indeterminate",
-    value: value === null ? 0 : value >= 0 && value <= 100 ? value : value < 0 ? 0 : 100
+    value: value === null || value === undefined ? 0 : value >= 0 && value <= 100 ? value : value < 0 ? 0 : 100
   }), helperText && /*#__PURE__*/_react["default"].createElement(HelperText, {
     overlay: overlay,
     backgroundType: backgroundType

package/progress-bar/ProgressBar.test.js

@@ -0,0 +1,65 @@
+"use strict";
+
+var _interopRequireDefault = require("@babel/runtime/helpers/interopRequireDefault");
+
+var _react = _interopRequireDefault(require("react"));
+
+var _react2 = require("@testing-library/react");
+
+var _ProgressBar = _interopRequireDefault(require("./ProgressBar"));
+
+describe("ProgressBar component tests", function () {
+  test("ProgressBar renders with label", function () {
+    var _render = (0, _react2.render)( /*#__PURE__*/_react["default"].createElement(_ProgressBar["default"], {
+      label: "test-label"
+    })),
+        getByText = _render.getByText;
+
+    expect(getByText("test-label")).toBeTruthy();
+  });
+  test("Overlay progressBar renders with label", function () {
+    var _render2 = (0, _react2.render)( /*#__PURE__*/_react["default"].createElement(_ProgressBar["default"], {
+      label: "test-label",
+      overlay: true
+    })),
+        getByText = _render2.getByText;
+
+    expect(getByText("test-label")).toBeTruthy();
+  });
+  test("ProgressBar renders with default value", function () {
+    var _render3 = (0, _react2.render)( /*#__PURE__*/_react["default"].createElement(_ProgressBar["default"], {
+      showValue: true
+    })),
+        getByText = _render3.getByText;
+
+    expect(getByText("0 %")).toBeTruthy();
+  });
+  test("Overlay progressBar renders with default value", function () {
+    var _render4 = (0, _react2.render)( /*#__PURE__*/_react["default"].createElement(_ProgressBar["default"], {
+      showValue: true,
+      overlay: true
+    })),
+        getByText = _render4.getByText;
+
+    expect(getByText("0 %")).toBeTruthy();
+  });
+  test("ProgressBar renders with value", function () {
+    var _render5 = (0, _react2.render)( /*#__PURE__*/_react["default"].createElement(_ProgressBar["default"], {
+      showValue: true,
+      value: 25
+    })),
+        getByText = _render5.getByText;
+
+    expect(getByText("25 %")).toBeTruthy();
+  });
+  test("Overlay progressBar renders with value", function () {
+    var _render6 = (0, _react2.render)( /*#__PURE__*/_react["default"].createElement(_ProgressBar["default"], {
+      showValue: true,
+      value: 25,
+      overlay: true
+    })),
+        getByText = _render6.getByText;
+
+    expect(getByText("25 %")).toBeTruthy();
+  });
+});

package/quick-nav/QuickNav.d.ts

@@ -0,0 +1,4 @@
+/// <reference types="react" />
+import QuickNavTypes from "./types";
+declare const DxcQuickNav: ({ title, links }: QuickNavTypes) => JSX.Element;
+export default DxcQuickNav;

package/quick-nav/QuickNav.js

@@ -0,0 +1,64 @@
+"use strict";
+
+var _interopRequireDefault = require("@babel/runtime/helpers/interopRequireDefault");
+
+Object.defineProperty(exports, "__esModule", {
+  value: true
+});
+exports["default"] = void 0;
+
+var _taggedTemplateLiteral2 = _interopRequireDefault(require("@babel/runtime/helpers/taggedTemplateLiteral"));
+
+var _react = _interopRequireDefault(require("react"));
+
+var _styledComponents = _interopRequireDefault(require("styled-components"));
+
+var _slugify = _interopRequireDefault(require("slugify"));
+
+var _Heading = _interopRequireDefault(require("../heading/Heading"));
+
+var _Stack = _interopRequireDefault(require("../stack/Stack"));
+
+var _Inset = _interopRequireDefault(require("../inset/Inset"));
+
+var _List = _interopRequireDefault(require("../list/List"));
+
+var _Text = _interopRequireDefault(require("../text/Text"));
+
+var _templateObject, _templateObject2;
+
+var DxcQuickNav = function DxcQuickNav(_ref) {
+  var title = _ref.title,
+      links = _ref.links;
+  return /*#__PURE__*/_react["default"].createElement(QuickNavContainer, null, /*#__PURE__*/_react["default"].createElement(_Stack["default"], {
+    gutter: "small"
+  }, /*#__PURE__*/_react["default"].createElement(_Heading["default"], {
+    level: 4,
+    text: title
+  }), /*#__PURE__*/_react["default"].createElement(_List["default"], null, links.map(function (link) {
+    var _link$links;
+
+    return /*#__PURE__*/_react["default"].createElement(_Inset["default"], {
+      space: "xxsmall"
+    }, /*#__PURE__*/_react["default"].createElement(_Text["default"], null, /*#__PURE__*/_react["default"].createElement(Link, {
+      href: "#".concat((0, _slugify["default"])(link === null || link === void 0 ? void 0 : link.label, {
+        lower: true
+      }))
+    }, link === null || link === void 0 ? void 0 : link.label), (_link$links = link.links) === null || _link$links === void 0 ? void 0 : _link$links.map(function (sublink) {
+      return /*#__PURE__*/_react["default"].createElement(_Inset["default"], {
+        horizontal: "xsmall"
+      }, /*#__PURE__*/_react["default"].createElement(_Text["default"], null, /*#__PURE__*/_react["default"].createElement(Link, {
+        href: "#".concat((0, _slugify["default"])(sublink === null || sublink === void 0 ? void 0 : sublink.label, {
+          lower: true
+        }))
+      }, sublink === null || sublink === void 0 ? void 0 : sublink.label)));
+    })));
+  }))));
+};
+
+var QuickNavContainer = _styledComponents["default"].div(_templateObject || (_templateObject = (0, _taggedTemplateLiteral2["default"])(["\n  padding: 5px 15px;\n  border-left: 2px solid #bfbfbf;\n  li {\n    div:first-child {\n      display: none;\n    }\n  }\n"])));
+
+var Link = _styledComponents["default"].a(_templateObject2 || (_templateObject2 = (0, _taggedTemplateLiteral2["default"])(["\n  text-decoration: none;\n  font-size: 14px;\n  color: #666666;\n  &:hover {\n    color: #ab63cf;\n  }\n  &:focus {\n    border-radius: 2px;\n    border-color: #0095ff;\n  }\n"])));
+
+var _default = DxcQuickNav;
+exports["default"] = _default;

package/quick-nav/QuickNav.stories.tsx

@@ -0,0 +1,237 @@
+import React from "react";
+import styled from "styled-components";
+import DxcQuickNav from "./QuickNav";
+import DxcHeading from "../heading/Heading";
+import DxcText from "../text/Text";
+import Title from "../../.storybook/components/Title";
+import ExampleContainer from "../../.storybook/components/ExampleContainer";
+
+export default {
+  title: "QuickNav",
+  component: DxcQuickNav,
+};
+
+const links = [
+  {
+    label: "Overview",
+    id: "overview",
+    links: [
+      {
+        label: "Introduction",
+        id: "introduction",
+      },
+    ],
+  },
+  {
+    label: "Principles",
+    id: "principles",
+    links: [
+      { label: "Color", id: "color" },
+      { label: "Spacing", id: "spacing" },
+      { label: "Typography", id: "typography" },
+    ],
+  },
+];
+
+export const Chromatic = () => (
+  <>
+    <ExampleContainer>
+      <Title title="Default" level={4} />
+      <QuickNavContainer>
+        <DxcQuickNav title="Sections" links={links}></DxcQuickNav>
+      </QuickNavContainer>
+    </ExampleContainer>
+    <ExampleContainer pseudoState="pseudo-hover">
+      <Title title="Link hovered" level={4} />
+      <QuickNavContainer>
+        <DxcQuickNav title="Sections" links={links}></DxcQuickNav>
+      </QuickNavContainer>
+    </ExampleContainer>
+    <ExampleContainer>
+      <Title title="QuickNav with content" level={4} />
+      <Container>
+        <ContentContainer>
+          <Content id="overview">
+            <DxcHeading level={1} text="Overview" margin={{ bottom: "small" }} />
+            <DxcText>
+              Halstack is the DXC Technology's open source design system for insurance products and digital experiences.
+              Our system provides all the tools and resources needed to create superior, beautiful but above all,
+              functional user experiences. Halstack is the DXC Technology's open source design system for insurance
+              products and digital experiences. Our system provides all the tools and resources needed to create
+              superior, beautiful but above all, functional user experiences.Halstack is the DXC Technology's open
+              source design system for insurance products and digital experiences. Our system provides all the tools and
+              resources needed to create superior, beautiful but above all, functional user experiences.Halstack is the
+              DXC Technology's open source design system for insurance products and digital experiences. Our system
+              provides all the tools and resources needed to create superior, beautiful but above all, functional user
+              experiences.Halstack is the DXC Technology's open source design system for insurance products and digital
+              experiences. Our system provides all the tools and resources needed to create superior, beautiful but
+              above all, functional user experiences.Halstack is the DXC Technology's open source design system for
+              insurance products and digital experiences. Our system provides all the tools and resources needed to
+              create superior, beautiful but above all, functional user experiences.Halstack is the DXC Technology's
+              open source design system for insurance products and digital experiences. Our system provides all the
+              tools and resources needed to create superior, beautiful but above all, functional user experiences.
+            </DxcText>
+            <Content id="introduction">
+              <DxcHeading level={2} text="Introduction" margin={{ top: "xsmall", bottom: "xsmall" }} />
+              <DxcText>
+                Design principles Halstack design principles are the fundamental part of DXC Technology's approach to
+                provide guidance for development teams in order to deliver delightful and consistent user experiences to
+                our customers: Balance Consistency Visual hierarchy All our components, design tokens, accessibility
+                guidelines, responsive design techniques, and layout proposals have been carefully curated by DXC design
+                and engineering teams with the objective of creating a unique visual language and ecosystem for our
+                applications. This is the DXC way of creating User Experiences. Open Source Halstack is an open source
+                design system, this means that we work towards DXC Technology bussines needs, but it is open for anyone
+                to use and contribute back to. We are charmed to receive external contributions to help us find bugs,
+                design new features, or help us improve the project documentation. If you're interested, definitely
+                check out our contribution guidelines.Design principles Halstack design principles are the fundamental
+                part of DXC Technology's approach to provide guidance for development teams in order to deliver
+                delightful and consistent user experiences to our customers: Balance Consistency Visual hierarchy All
+                our components, design tokens, accessibility guidelines, responsive design techniques, and layout
+                proposals have been carefully curated by DXC design and engineering teams with the objective of creating
+                a unique visual language and ecosystem for our applications. This is the DXC way of creating User
+                Experiences. Open Source Halstack is an open source design system, this means that we work towards DXC
+                Technology bussines needs, but it is open for anyone to use and contribute back to. We are charmed to
+                receive external contributions to help us find bugs, design new features, or help us improve the project
+                documentation. If you're interested, definitely check out our contribution guidelines.Design principles
+                Halstack design principles are the fundamental part of DXC Technology's approach to provide guidance for
+                development teams in order to deliver delightful and consistent user experiences to our customers:
+                Balance Consistency Visual hierarchy All our components, design tokens, accessibility guidelines,
+                responsive design techniques, and layout proposals have been carefully curated by DXC design and
+                engineering teams with the objective of creating a unique visual language and ecosystem for our
+                applications. This is the DXC way of creating User Experiences. Open Source Halstack is an open source
+                design system, this means that we work towards DXC Technology bussines needs, but it is open for anyone
+                to use and contribute back to. We are charmed to receive external contributions to help us find bugs,
+                design new features, or help us improve the project documentation. If you're interested, definitely
+                check out our contribution guidelines.
+              </DxcText>
+            </Content>
+          </Content>
+          <Content id="principles">
+            <DxcHeading level={1} text="Principles" margin={{ top: "small", bottom: "xsmall" }} />
+            <Content id="color">
+              <DxcHeading level={2} text="Color" margin={{ top: "xsmall", bottom: "xsmall" }} />
+              <DxcText>
+                The color palette is an essential asset as a communication resource of our design system. Halstack color
+                palette brings a unified consistency and helps in guiding the user's perception order. Our color palette
+                is based in the HSL model . All our color families are calculated using the lightness value of the
+                standard DXC palette colors. Color Tokens Halstack uses tokens to manage color. Appart from a
+                multi-purpose greyscale family, purple and blue are the core color families used in our set of
+                components. Additional families as red, green and yellow help as feedback role-based color palettes and
+                must not be used outside this context.The color palette is an essential asset as a communication
+                resource of our design system. Halstack color palette brings a unified consistency and helps in guiding
+                the user's perception order. Our color palette is based in the HSL model . All our color families are
+                calculated using the lightness value of the standard DXC palette colors. Color Tokens Halstack uses
+                tokens to manage color. Appart from a multi-purpose greyscale family, purple and blue are the core color
+                families used in our set of components. Additional families as red, green and yellow help as feedback
+                role-based color palettes and must not be used outside this context.The color palette is an essential
+                asset as a communication resource of our design system. Halstack color palette brings a unified
+                consistency and helps in guiding the user's perception order. Our color palette is based in the HSL
+                model . All our color families are calculated using the lightness value of the standard DXC palette
+                colors. Color Tokens Halstack uses tokens to manage color. Appart from a multi-purpose greyscale family,
+                purple and blue are the core color families used in our set of components. Additional families as red,
+                green and yellow help as feedback role-based color palettes and must not be used outside this
+                context.The color palette is an essential asset as a communication resource of our design system.
+                Halstack color palette brings a unified consistency and helps in guiding the user's perception order.
+                Our color palette is based in the HSL model . All our color families are calculated using the lightness
+                value of the standard DXC palette colors. Color Tokens Halstack uses tokens to manage color. Appart from
+                a multi-purpose greyscale family, purple and blue are the core color families used in our set of
+                components. Additional families as red, green and yellow help as feedback role-based color palettes and
+                must not be used outside this context.The color palette is an essential asset as a communication
+                resource of our design system. Halstack color palette brings a unified consistency and helps in guiding
+                the user's perception order. Our color palette is based in the HSL model . All our color families are
+                calculated using the lightness value of the standard DXC palette colors. Color Tokens Halstack uses
+                tokens to manage color. Appart from a multi-purpose greyscale family, purple and blue are the core color
+                families used in our set of components. Additional families as red, green and yellow help as feedback
+                role-based color palettes and must not be used outside this context.
+              </DxcText>
+            </Content>
+            <Content id="spacing">
+              <DxcHeading level={2} text="Spacing" margin={{ top: "xsmall", bottom: "xsmall" }} />
+              <DxcText>
+                In the search of consistent alignment between the elements we provide a spacing scale based on a root
+                values of 8px and 4px. The numbers 4 and 8 are easily multiplied, they provide flexible and consistent,
+                yet distinct enough, steps between them.In the search of consistent alignment between the elements we
+                provide a spacing scale based on a root values of 8px and 4px. The numbers 4 and 8 are easily
+                multiplied, they provide flexible and consistent, yet distinct enough, steps between them.In the search
+                of consistent alignment between the elements we provide a spacing scale based on a root values of 8px
+                and 4px. The numbers 4 and 8 are easily multiplied, they provide flexible and consistent, yet distinct
+                enough, steps between them.In the search of consistent alignment between the elements we provide a
+                spacing scale based on a root values of 8px and 4px. The numbers 4 and 8 are easily multiplied, they
+                provide flexible and consistent, yet distinct enough, steps between them.In the search of consistent
+                alignment between the elements we provide a spacing scale based on a root values of 8px and 4px. The
+                numbers 4 and 8 are easily multiplied, they provide flexible and consistent, yet distinct enough, steps
+                between them.In the search of consistent alignment between the elements we provide a spacing scale based
+                on a root values of 8px and 4px. The numbers 4 and 8 are easily multiplied, they provide flexible and
+                consistent, yet distinct enough, steps between them.In the search of consistent alignment between the
+                elements we provide a spacing scale based on a root values of 8px and 4px. The numbers 4 and 8 are
+                easily multiplied, they provide flexible and consistent, yet distinct enough, steps between them.
+              </DxcText>
+            </Content>
+            <Content id="typography">
+              <DxcHeading level={2} text="Typography" margin={{ top: "xsmall", bottom: "xsmall" }} />
+              <DxcText>
+                Our selected typography helps in structuring our user's experience based on the visual impact that it
+                has on the user interface content. It defines what is the first noticeable piece of information or data
+                based on the font shape, size, color, or type and it highlights some pieces of text over the rest. Some
+                typographic elements used in Halstack Design System include headers, body, taglines, captions, and
+                labels. Make sure you include all the different typographic variants in order to enhance the
+                application's content structure, including the Heading component which defines different levels of page
+                and section titles.Our selected typography helps in structuring our user's experience based on the
+                visual impact that it has on the user interface content. It defines what is the first noticeable piece
+                of information or data based on the font shape, size, color, or type and it highlights some pieces of
+                text over the rest. Some typographic elements used in Halstack Design System include headers, body,
+                taglines, captions, and labels. Make sure you include all the different typographic variants in order to
+                enhance the application's content structure, including the Heading component which defines different
+                levels of page and section titles.Our selected typography helps in structuring our user's experience
+                based on the visual impact that it has on the user interface content. It defines what is the first
+                noticeable piece of information or data based on the font shape, size, color, or type and it highlights
+                some pieces of text over the rest. Some typographic elements used in Halstack Design System include
+                headers, body, taglines, captions, and labels. Make sure you include all the different typographic
+                variants in order to enhance the application's content structure, including the Heading component which
+                defines different levels of page and section titles.Our selected typography helps in structuring our
+                user's experience based on the visual impact that it has on the user interface content. It defines what
+                is the first noticeable piece of information or data based on the font shape, size, color, or type and
+                it highlights some pieces of text over the rest. Some typographic elements used in Halstack Design
+                System include headers, body, taglines, captions, and labels. Make sure you include all the different
+                typographic variants in order to enhance the application's content structure, including the Heading
+                component which defines different levels of page and section titles.Our selected typography helps in
+                structuring our user's experience based on the visual impact that it has on the user interface content.
+                It defines what is the first noticeable piece of information or data based on the font shape, size,
+                color, or type and it highlights some pieces of text over the rest. Some typographic elements used in
+                Halstack Design System include headers, body, taglines, captions, and labels. Make sure you include all
+                the different typographic variants in order to enhance the application's content structure, including
+                the Heading component which defines different levels of page and section titles.
+              </DxcText>
+            </Content>
+          </Content>
+        </ContentContainer>
+        <QuickNavContainer>
+          <DxcQuickNav title="Sections" links={links}></DxcQuickNav>
+        </QuickNavContainer>
+      </Container>
+    </ExampleContainer>
+  </>
+);
+
+const Container = styled.div`
+  display: flex;
+  flex-direction: row;
+  width: 100%;
+`;
+
+const ContentContainer = styled.div`
+  display: flex;
+  flex-direction: column;
+  padding: 60px;
+  margin: 0 auto;
+  width: 800px;
+`;
+
+const Content = styled.div``;
+
+const QuickNavContainer = styled.div`
+  max-height: calc(100vh - 100px);
+  position: sticky;
+  top: 100px;
+  width: 300px;
+`;

package/quick-nav/types.d.ts

@@ -0,0 +1,21 @@
+declare type Props = {
+    /**
+     * Title of the quick nav component.
+     */
+    title: string;
+    /**
+     * Links to be shown inside the quick nav component.
+     */
+    links: Link[];
+};
+declare type Link = {
+    /**
+     * Label to be shown in the link.
+     */
+    label: string;
+    /**
+     * Sublinks of the link.
+     */
+    links?: Link[];
+};
+export default Props;

package/quick-nav/types.js

@@ -0,0 +1,5 @@
+"use strict";
+
+Object.defineProperty(exports, "__esModule", {
+  value: true
+});

package/radio/Radio.js

@@ -27,9 +27,9 @@ var _variables = require("../common/variables.js");
 
 var _utils = require("../common/utils.js");
 
-var _useTheme = _interopRequireDefault(require("../useTheme.js"));
+var _useTheme = _interopRequireDefault(require("../useTheme"));
 
-var _BackgroundColorContext = _interopRequireDefault(require("../BackgroundColorContext.js"));
+var _BackgroundColorContext = _interopRequireDefault(require("../BackgroundColorContext"));
 
 var _templateObject, _templateObject2;
 

package/radio/Radio.test.js

@@ -0,0 +1,71 @@
+"use strict";
+
+var _interopRequireDefault = require("@babel/runtime/helpers/interopRequireDefault");
+
+var _react = _interopRequireDefault(require("react"));
+
+var _react2 = require("@testing-library/react");
+
+var _Radio = _interopRequireDefault(require("./Radio"));
+
+describe("Radio component tests", function () {
+  test("Radio renders correctly", function () {
+    var _render = (0, _react2.render)( /*#__PURE__*/_react["default"].createElement(_Radio["default"], {
+      label: "Radio button"
+    })),
+        getByText = _render.getByText;
+
+    expect(getByText("Radio button")).toBeTruthy();
+  });
+  test("Calls correct function on click", function () {
+    var onClick = jest.fn();
+
+    var _render2 = (0, _react2.render)( /*#__PURE__*/_react["default"].createElement(_Radio["default"], {
+      label: "Radio button",
+      onClick: onClick
+    })),
+        getByText = _render2.getByText;
+
+    _react2.fireEvent.click(getByText("Radio button"));
+
+    expect(onClick).toHaveBeenCalled();
+    expect(onClick).toHaveBeenCalledWith(true);
+  });
+  test("Controlled Radio", function () {
+    var onClick = jest.fn();
+
+    var _render3 = (0, _react2.render)( /*#__PURE__*/_react["default"].createElement(_Radio["default"], {
+      label: "Radio button",
+      checked: false,
+      onClick: onClick
+    })),
+        getByText = _render3.getByText,
+        getByRole = _render3.getByRole;
+
+    expect(getByRole("radio").checked).toBe(false);
+
+    _react2.fireEvent.click(getByText("Radio button"));
+
+    expect(onClick).toHaveBeenCalled();
+    expect(onClick).toHaveBeenCalledWith(true);
+    expect(getByRole("radio").checked).toBe(false);
+  });
+  test("Uncontrolled Radio", function () {
+    var onClick = jest.fn();
+
+    var _render4 = (0, _react2.render)( /*#__PURE__*/_react["default"].createElement(_Radio["default"], {
+      label: "Radio button",
+      onClick: onClick
+    })),
+        getByText = _render4.getByText,
+        getByRole = _render4.getByRole;
+
+    expect(getByRole("radio").checked).toBe(false);
+
+    _react2.fireEvent.click(getByText("Radio button"));
+
+    expect(onClick).toHaveBeenCalled();
+    expect(onClick).toHaveBeenCalledWith(true);
+    expect(getByRole("radio").checked).toBe(false);
+  });
+});

package/radio-group/Radio.d.ts

@@ -0,0 +1,4 @@
+import React from "react";
+import { RadioProps } from "./types";
+declare const _default: React.MemoExoticComponent<({ option, currentValue, onClick, error, disabled, focused, readonly, tabIndex, }: RadioProps) => JSX.Element>;
+export default _default;