@elastic/eui 73.0.0 → 74.0.0

package/es/services/url.js

@@ -1,23 +0,0 @@
-/*
- * Copyright Elasticsearch B.V. and/or licensed to Elasticsearch B.V. under one
- * or more contributor license agreements. Licensed under the Elastic License
- * 2.0 and the Server Side Public License, v 1; you may not use this file except
- * in compliance with, at your election, the Elastic License 2.0 or the Server
- * Side Public License, v 1.
- */
-var isElasticHost = /^([a-zA-Z0-9]+\.)*elastic\.co$/; // In order for the domain to be secure it needs to be in a parsable format,
-// with the protocol of http: or https: and the host matching elastic.co or
-// of one its subdomains
-
-export var isDomainSecure = function isDomainSecure() {
-  var url = arguments.length > 0 && arguments[0] !== undefined ? arguments[0] : '';
-
-  try {
-    var parsed = new URL(url);
-    var protocolMatches = parsed.protocol === 'http:' || parsed.protocol === 'https:';
-    var domainMatches = !!parsed.host.match(isElasticHost);
-    return protocolMatches && domainMatches;
-  } catch (e) {
-    return false;
-  }
-};

package/lib/services/url.js

@@ -1,32 +0,0 @@
-"use strict";
-
-Object.defineProperty(exports, "__esModule", {
-  value: true
-});
-exports.isDomainSecure = void 0;
-
-/*
- * Copyright Elasticsearch B.V. and/or licensed to Elasticsearch B.V. under one
- * or more contributor license agreements. Licensed under the Elastic License
- * 2.0 and the Server Side Public License, v 1; you may not use this file except
- * in compliance with, at your election, the Elastic License 2.0 or the Server
- * Side Public License, v 1.
- */
-var isElasticHost = /^([a-zA-Z0-9]+\.)*elastic\.co$/; // In order for the domain to be secure it needs to be in a parsable format,
-// with the protocol of http: or https: and the host matching elastic.co or
-// of one its subdomains
-
-var isDomainSecure = function isDomainSecure() {
-  var url = arguments.length > 0 && arguments[0] !== undefined ? arguments[0] : '';
-
-  try {
-    var parsed = new URL(url);
-    var protocolMatches = parsed.protocol === 'http:' || parsed.protocol === 'https:';
-    var domainMatches = !!parsed.host.match(isElasticHost);
-    return protocolMatches && domainMatches;
-  } catch (e) {
-    return false;
-  }
-};
-
-exports.isDomainSecure = isDomainSecure;

package/optimize/es/services/url.js

@@ -1,23 +0,0 @@
-/*
- * Copyright Elasticsearch B.V. and/or licensed to Elasticsearch B.V. under one
- * or more contributor license agreements. Licensed under the Elastic License
- * 2.0 and the Server Side Public License, v 1; you may not use this file except
- * in compliance with, at your election, the Elastic License 2.0 or the Server
- * Side Public License, v 1.
- */
-var isElasticHost = /^([a-zA-Z0-9]+\.)*elastic\.co$/; // In order for the domain to be secure it needs to be in a parsable format,
-// with the protocol of http: or https: and the host matching elastic.co or
-// of one its subdomains
-
-export var isDomainSecure = function isDomainSecure() {
-  var url = arguments.length > 0 && arguments[0] !== undefined ? arguments[0] : '';
-
-  try {
-    var parsed = new URL(url);
-    var protocolMatches = parsed.protocol === 'http:' || parsed.protocol === 'https:';
-    var domainMatches = !!parsed.host.match(isElasticHost);
-    return protocolMatches && domainMatches;
-  } catch (e) {
-    return false;
-  }
-};

package/optimize/lib/services/url.js

@@ -1,32 +0,0 @@
-"use strict";
-
-Object.defineProperty(exports, "__esModule", {
-  value: true
-});
-exports.isDomainSecure = void 0;
-
-/*
- * Copyright Elasticsearch B.V. and/or licensed to Elasticsearch B.V. under one
- * or more contributor license agreements. Licensed under the Elastic License
- * 2.0 and the Server Side Public License, v 1; you may not use this file except
- * in compliance with, at your election, the Elastic License 2.0 or the Server
- * Side Public License, v 1.
- */
-var isElasticHost = /^([a-zA-Z0-9]+\.)*elastic\.co$/; // In order for the domain to be secure it needs to be in a parsable format,
-// with the protocol of http: or https: and the host matching elastic.co or
-// of one its subdomains
-
-var isDomainSecure = function isDomainSecure() {
-  var url = arguments.length > 0 && arguments[0] !== undefined ? arguments[0] : '';
-
-  try {
-    var parsed = new URL(url);
-    var protocolMatches = parsed.protocol === 'http:' || parsed.protocol === 'https:';
-    var domainMatches = !!parsed.host.match(isElasticHost);
-    return protocolMatches && domainMatches;
-  } catch (e) {
-    return false;
-  }
-};
-
-exports.isDomainSecure = isDomainSecure;

package/src/components/basic_table/_basic_table.scss

@@ -1,41 +0,0 @@
-.euiBasicTable {
-  &-loading {
-    position: relative;
-
-    tbody {
-      overflow: hidden;
-    }
-
-    tbody::before {
-      position: absolute;
-      content: '';
-      width: 100%;
-      height: $euiBorderWidthThick;
-      background-color: $euiColorPrimary;
-      animation: euiBasicTableLoading 1000ms linear;
-      animation-iteration-count: infinite;
-    }
-  }
-}
-
-@keyframes euiBasicTableLoading {
-  from {
-    left: 0;
-    width: 0;
-  }
-
-  20% {
-    left: 0;
-    width: 40%;
-  }
-
-  80% {
-    left: 60%;
-    width: 40%;
-  }
-
-  100% {
-    left: 100%;
-    width: 0;
-  }
-}

package/src/components/basic_table/_index.scss

@@ -1 +0,0 @@
-@import 'basic_table';

package/src/components/date_picker/react-datepicker/LICENSE

@@ -1,21 +0,0 @@
-The MIT License (MIT)
-
-Copyright (c) 2018 HackerOne Inc and individual contributors
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.

package/src/components/date_picker/react-datepicker/README.md

@@ -1,168 +0,0 @@
-_Forked by @elastic/eui from Hacker0x01/react-datepicker for accessibility and consolidation of services._
-
-Decision to not use a more traditional "vendor" directory approach includes redundant services, unnecessary dependencies, and a separate build pipeline. Most notably, `react-datepicker` included third-party popover and focus trap service and components that do not align with EUI interaction standards and were replaced, at parity, with EUI components.
-
-Other modifications:
-
-* Changed to `.js` naming to conform to EUI build processes
-* Removed files related to repository management and publishing
-* Adjusted `babel.rc` and `package.json` naming to avoid babel configuration conflicts
-
-___
-# React Date Picker
-
-[![npm version](https://badge.fury.io/js/react-datepicker.svg)](https://badge.fury.io/js/react-datepicker)
-[![Build Status](https://travis-ci.org/Hacker0x01/react-datepicker.svg?branch=master)](https://travis-ci.org/Hacker0x01/react-datepicker)
-[![Dependency Status](https://david-dm.org/Hacker0x01/react-datepicker.svg)](https://david-dm.org/Hacker0x01/react-datepicker)
-[![codecov](https://codecov.io/gh/Hacker0x01/react-datepicker/branch/master/graph/badge.svg)](https://codecov.io/gh/Hacker0x01/react-datepicker)
-[![Downloads](http://img.shields.io/npm/dm/react-datepicker.svg)](https://npmjs.org/package/react-datepicker)
-[![Code Quality: Javascript](https://img.shields.io/lgtm/grade/javascript/g/Hacker0x01/react-datepicker.svg?logo=lgtm&logoWidth=18)](https://lgtm.com/projects/g/Hacker0x01/react-datepicker/context:javascript)
-[![Total Alerts](https://img.shields.io/lgtm/alerts/g/Hacker0x01/react-datepicker.svg?logo=lgtm&logoWidth=18)](https://lgtm.com/projects/g/Hacker0x01/react-datepicker/alerts)
-
-A simple and reusable Datepicker component for React ([Demo](https://reactdatepicker.com/))
-
-![](https://cloud.githubusercontent.com/assets/1412392/5339491/c40de124-7ee1-11e4-9f07-9276e2545f27.png)
-
-## Installation
-
-The package can be installed via NPM:
-
-```
-npm install react-datepicker --save
-```
-
-You’ll need to install React, PropTypes, and Moment.js separately since those dependencies aren’t included in the package. Below is a simple example of how to use the Datepicker in a React view. You will also need to require the CSS file from this package (or provide your own). The example below shows how to include the CSS from this package if your build system supports requiring CSS files (Webpack is one that does).
-
-```js
-import React from "react";
-import DatePicker from "react-datepicker";
-import moment from "moment";
-
-import "react-datepicker/dist/react-datepicker.css";
-
-// CSS Modules, react-datepicker-cssmodules.css
-// import 'react-datepicker/dist/react-datepicker-cssmodules.css';
-
-class Example extends React.Component {
-  constructor(props) {
-    super(props);
-    this.state = {
-      startDate: moment()
-    };
-    this.handleChange = this.handleChange.bind(this);
-  }
-
-  handleChange(date) {
-    this.setState({
-      startDate: date
-    });
-  }
-
-  render() {
-    return (
-      <DatePicker
-        selected={this.state.startDate}
-        onChange={this.handleChange}
-      />
-    );
-  }
-}
-```
-
-## Configuration
-
-The most basic use of the DatePicker can be described with:
-
-```js
-<DatePicker selected={this.state.date} onChange={this.handleChange} />
-```
-
-You can use `onSelect` event handler which fires each time some calendar date has been selected
-
-```js
-<DatePicker
-  selected={this.state.date}
-  onSelect={this.handleSelect} //when day is clicked
-  onChange={this.handleChange} //only when value has changed
-/>
-```
-
-`onClickOutside` handler may be useful to close datepicker in `inline` mode
-
-See [here](https://github.com/Hacker0x01/react-datepicker/blob/master/docs/datepicker.md) for a full list of props that may be passed to the component. Examples are given on the [main website](https://hacker0x01.github.io/react-datepicker).
-
-### Time picker
-
-You can also include a time picker by adding the showTimeSelect prop
-
-```js
-<DatePicker
-  selected={this.state.date}
-  onChange={this.handleChange}
-  showTimeSelect
-  dateFormat="LLL"
-/>
-```
-
-Times will be displayed at 30-minute intervals by default (default configurable via timeInterval prop)
-
-More examples of how to use the time picker are given on the [main website](https://hacker0x01.github.io/react-datepicker)
-
-### Localization
-
-The date picker relies on [moment.js internationalization](http://momentjs.com/docs/#/i18n/) to localize its display components. By default, the date picker will use the locale globally set in moment, which is English. Locales can be changed in the following ways:
-
-* **Globally** by calling `moment.locale(lang)`
-* **Picker-specific** by providing the `locale` prop
-
-Locales can be further configured in moment with various [customization options](http://momentjs.com/docs/#/customization/).
-
-_As of version 0.23, the `weekdays` and `weekStart` DatePicker props have been removed. Instead, they can be configured with the `weekdaysMin` and `week.dow` moment locale customization options._
-
-## Compatibility
-
-### React
-
-We're always trying to stay compatible with the latest version of React. We can't support all older versions of React.
-
-Latest compatible versions:
-
-* React 15.5 or newer: All above React-datepicker v.0.40.0
-* React 15.4.1: needs React-datepicker v0.40.0, newer won't work (due to react-onclickoutside dependencies)
-* React 0.14 or newer: All above React-datepicker v0.13.0
-* React 0.13: React-datepicker v0.13.0
-* pre React 0.13: React-datepicker v0.6.2
-
-### Browser Support
-
-The date picker is compatible with the latest versions of Chrome, Firefox, and IE10+.
-
-Unfortunately, it is difficult to support legacy browsers while maintaining our ability to develop new features in the future. For IE9 support, it is known that the [classlist polyfill](https://www.npmjs.com/package/classlist-polyfill) is needed, but this may change or break at any point in the future.
-
-## Local Development
-
-The `master` branch contains the latest version of the Datepicker component. To start your example app, you can run `yarn start`. This starts a simple webserver on http://localhost:8080.
-
-You can run `yarn test` to execute the test suite and linters. To help you develop the component we’ve set up some tests that cover the basic functionality (can be found in `/tests`). Even though we’re big fans of testing, this only covers a small piece of the component. We highly recommend you add tests when you’re adding new functionality.
-
-### The examples
-
-The examples are hosted within the docs folder and are ran in the simple app that loads the Datepicker. To extend the examples with a new example, you can simply duplicate one of the existing examples and change the unique properties of your example.
-
-## Accessibility
-
-### Keyboard support
-
-* _Left_: Move to the previous day.
-* _Right_: Move to the next day.
-* _Up_: Move to the previous week.
-* _Down_: Move to the next week.
-* _PgUp_: Move to the previous month.
-* _PgDn_: Move to the next month.
-* _Home_: Move to the previous year.
-* _End_: Move to the next year.
-* _Enter/Esc/Tab_: close the calendar. (Enter & Esc calls preventDefault)
-
-## License
-
-Copyright (c) 2018 HackerOne Inc. and individual contributors. Licensed under MIT license, see [LICENSE](LICENSE) for the full license.

package/src/services/theme/README.md

@@ -1,153 +0,0 @@
-# JavaScript-based theming in EUI
-
-The style system to replace Sass and Sass-based design tokens in EUI.
-
-* Theme construction via a Proxy-based system with cascading and computed values
-  * Proxy-based: allows for the theme system to reference its own values (for reuse or for computational manipulation)
-  * Cascading: conceptually similar to Sass, where variable location and order are important
-  * Extendable: allows for appending style variables to the EUI theme structure, scoped to a React context provider
-  * Override-able: all theme tokens/variables can be altered by consumers
-* Theme consumption via React hook and HOC methods
-* Color mode support as first-class consideration
-  * "Light" and "dark" mode accounting
-  * Theme consumption is scoped to the current color mode (set in the context provider)
-* Style adaptaion based on a smal set of base values
-  * Text colors are calculated with WCAG Level AA (4.5:1) in mind
-  * Scalable typographic and spacing rhythms 
-
-
-## Layers of the theme system
-
-### Unbuilt theme
-
-_See [`euiThemeDefault`](../../themes/eui/theme.ts)_
-An unbuilt theme is a composed object of style values or `computed` functions.
-
-#### Style values
-
-Think design tokens or CSS property values. Ready to be consumed as-is in an application environment, using some JavaScript method of applying styles (i.e., a CSS-in-JS library is not required).
-
-#### `computed` functions
-
-These properties specify that the value depends upon some other value in the theme, in the shape of:
-
-```js
-computed(
-  ([size]) => size * 2 // predicate. What to do with the dependency values,
-  ['sizes.euiSize'], // dependency array, referencing other properties in the theme object
-)
-```
-
-The dependency array is optional. Omitting the array gives access to the computed theme.
-
-```js
-computed(
-  (theme) => theme.sizes.euiSize * 2
-)
-```
-
-### Theme system (built theme)
-
-_See [`EuiThemeDefault`](../../themes/eui/theme.ts)_
-A built theme by way of `buildTheme`, which transforms the object containing static style values and `computed` functions into a JavaScript Proxy object with handler traps. In this state, the theme is essentially inaccessible and immutable, that is, it requires `getComputed` to correctly order and access values and dependencies, and `set()` is disabled.
-
-### Computed theme
-
-_See [`EuiThemeContext`](../../themes/eui/context.ts)_
-A consumable theme object in which all `computed` function values have been computed; all values are accessible and usable in an application environment.
-Returned from `getComputed`, in the shape of:
-
-```js
-getComputed(
-  EuiThemeDefault, // Theme system (Proxy)
-  {}, // Modifications object
-  'light' // Color mode
-)
-```
-
-#### Modifications
-
-Because the theme system (built theme) is immutable, modifications can only be made at compute time by providing overrides and extensions for theme property values. These modifications are passed to the `EuiThemeProvider` via the `modify` prop and should match the high-level object shape of the theme. 
-
-#### Color mode
-
-Think light and dark mode. A theme has built-in color mode support, using the reserved `LIGHT` and `DARK` keys as a marker:
-
-```js
-colors: {
-  LIGHT: {...}
-  DARK : {...}
-}
-```
-The reserved color mode keys can be used at any level and location in a theme.
-`getComputed` will only compute and return values in the specified current color mode.
-
-
-## React-specific context
-
-### EuiThemeProvider
-
-_See [`EuiThemeProvider`](../../themes/eui/provider.ts)_
-Umbrella provider component that holds the various top-level theme configuration option providers: theme system, color mode, modifications; as well as the primary output provider: computed theme.
-The actual computation for computed theme values takes place at this level, where the three inputs are known (theme system, color mode, modifications) and the output (computed theme) can be cached for consumption. Input changes are captured and the output is recomputed.
-
-```js
-<EuiThemeProvider
-  theme={DefaultEuiTheme}
-  colorMode="light"
-  modify={{}}
-  />
-```
-
-All three props are optional. The default values for EUI will be used in the event that no configuration is provided. Note, however that colorMode switching will require consumers to maintain that app state.
-
-### useEuiTheme
-
-_See [`useEuiTheme`](../../themes/eui/hooks.tsx)_
-A custom React hook that returns the computed theme. This hook is little more than a wrapper around the `useContext` hook, accessing three of the top-level providers: computed theme, color mode, and modifications.
-
-```js
-const { euiTheme, colorMode, modifications } = useEuiTheme();
-```
-
-The `euiTheme` variable has TypeScript support, which will result in IDE autocomplete availability.
-
-### WithEuiTheme
-A higher-order-component that wraps `useEuiTheme` for React class components.
-
-
-___
-
-
-## Emotion
-
-[Emotion](https://emotion.sh/docs/introduction) is the CSS-in-JS library currently selected for use in EUI. Nothing in the EUI theming system is dependent upon Emotion packages, but the Emotion ecosystem will have impacts on generated styles.
-
-### Composition
-
-* Prefer the use of [`css` prop](https://emotion.sh/docs/css-prop) construction over [styled-component-like](https://emotion.sh/docs/styled) component construction
-* Babel-based build accommodation
-
-### Testing
-
-Snapshot testing ([as currently configured](https://emotion.sh/docs/testing#writing-a-test)) will result in generic `emotion-${n}` class names with the generated style object as part of the snapshot.
-
-* This seems good for EUI, but it also affects consumers
-  * Consumers will need to use the `@emotion/jest` snapshot serializer to avoid class name churn.
-  * Not ideal; unsure of any other solutions
-* During the conversion process, the snapshot diffs will look less than ideal when using `shallow` (a single wrapper element; DOM itself is unchanged):
-
-```diff
--  <div
--    className="euiTableRowCell__mobileHeader euiTableRowCell--hideForDesktop"
-+  <EmotionCssPropInternal
-+    __EMOTION_LABEL_PLEASE_DO_NOT_USE__="EuiTableRowCell"
-+    __EMOTION_TYPE_PLEASE_DO_NOT_USE__="td"
-+    className="euiTableRowCell"
-+    style={
-+      Object {
-+        "width": undefined,
-+    }
-+      }
-    >
-```

package/src/test/README.md

@@ -1,59 +0,0 @@
-# Testing-related utilities
-
-EUI uses many of the utilities in this directory in its own Jest tests and, in case they are useful for consuming apps, exports them from `@elastic/eui/lib/test` (commonjs) and `@elastic/eui/es/test` (esm)
-
-### findTestSubject
-
-Provides a quick mechanism for searching an Enzyme-mounted component tree for an element with a specific `data-test-subj` attribute.
-
-```js
-// if mountedComponent contains e.g. <button data-test-subj="custom-button"/>, this would return that button
-const component = findTestSubject(mountedComponent, 'custom-button');
-```
-
-### startThrowingReactWarnings
-
-Patches `console.warn` and `console.error` to throw any warnings or errors, causing Jest to fail the test. This catches warnings emitted by React.
-
-### stopThrowingReactWarnings
-
-Must be called after `startThrowingReactWarnings`, this unpatches the console and restores normal functionality.
-
-### sleep
-
-Returns an `await`able promise that resolves after the specified duration.
-
-```js
-doSomeAction();
-await sleep(500); // wait 500ms
-expect(resultOfSomeAction);
-```
-
-### takeMountedSnapshot
-
-Use this function to generate a Jest snapshot of components that have been fully rendered using Enzyme's `mount` method. Typically, a mounted component will result in a snapshot containing both React components and HTML elements. This function removes the React components, leaving only HTML elements in the snapshot.
-
-This function takes an optional configuration as a second argument, which supports one option: `hasArrayOutput`. Enable this option if the mounted component has multiple direct children, otherwise only the first is included in the snapshot. 
-
-```js
-expect(
-  takeMountedSnapshot(mountedComponent, {
-    hasArrayOutput: true,
-  })
-).toMatchSnapshot();
-```
-
-### testCustomHook
-
-Use this function to execute a custom hook and access its return value, which can be passed to `expect` for verification. The function also returns a `getUpdatedState` method which will always return the hook's current state, in case some interaction with the react component causes an update.
-
-```js
-const {
-  return: hookReturnValue,
-  getUpdatedState,
-} = testCustomHook(() => useCellPopover());
-
-expect(hookReturnValue).to.equal(myExpectedValue);
-doSomeActions();
-expect(getUpdatedState()).to.equal(myExpectedValue);
-```

package/test-env/services/url.js

@@ -1,32 +0,0 @@
-"use strict";
-
-Object.defineProperty(exports, "__esModule", {
-  value: true
-});
-exports.isDomainSecure = void 0;
-
-/*
- * Copyright Elasticsearch B.V. and/or licensed to Elasticsearch B.V. under one
- * or more contributor license agreements. Licensed under the Elastic License
- * 2.0 and the Server Side Public License, v 1; you may not use this file except
- * in compliance with, at your election, the Elastic License 2.0 or the Server
- * Side Public License, v 1.
- */
-var isElasticHost = /^([a-zA-Z0-9]+\.)*elastic\.co$/; // In order for the domain to be secure it needs to be in a parsable format,
-// with the protocol of http: or https: and the host matching elastic.co or
-// of one its subdomains
-
-var isDomainSecure = function isDomainSecure() {
-  var url = arguments.length > 0 && arguments[0] !== undefined ? arguments[0] : '';
-
-  try {
-    var parsed = new URL(url);
-    var protocolMatches = parsed.protocol === 'http:' || parsed.protocol === 'https:';
-    var domainMatches = !!parsed.host.match(isElasticHost);
-    return protocolMatches && domainMatches;
-  } catch (e) {
-    return false;
-  }
-};
-
-exports.isDomainSecure = isDomainSecure;