@gitlab/ui 115.11.0 → 117.0.0

package/src/components/charts/legend/legend.md

@@ -1,16 +0,0 @@
-## Disabling Legends
-
-By default, to prevent the chart from disappearing, all legends can't be toggled off – the last
-active legend will be disabled. To manually disable a legend, pass it the
-`disabled` property in `seriesInfo`:
-
-```js
-seriesInfo = [
-  {
-    name: 'Example Legend',
-    color: 'blue',
-    disabled: true,
-    type: 'line'
-  }
-]
-```

package/src/components/charts/line/line.md

@@ -1,7 +0,0 @@
-This is a basic line chart.
-
-### Implementation Details
-
-This component wraps the GitLab UI `chart` component, which in turn wraps the ECharts component.
-
-See the [chart](./?path=/story/charts-chart--default) component for more info.

package/src/components/charts/series_label/series_label.md

@@ -1 +0,0 @@
-Displays chart data series name as a label for chart legend, tooltip, etc.

package/src/components/charts/shared/tooltip/tooltip.md

@@ -1,3 +0,0 @@
-### ECharts custom tooltip
-
-Uses GitLab UI's `popover` component in lieu of echart's tooltip.

package/src/components/charts/single_stat/single_stat.md

@@ -1,8 +0,0 @@
-The single stat component is used to show a single value. The color of the meta icon / badge is
-determined by the **variant** prop, which can be one of "success", "warning", "danger", "info",
-"neutral" or "muted" (default).
-
-#### Hover state
-
-You can make the component focusable by adding a `tabindex=0` attribute to it. This will also apply
-a hover state to the component.

package/src/components/charts/sparkline/sparkline.md

@@ -1,8 +0,0 @@
-
-This is a basic sparkline chart.
-
-### Implementation Details
-
-This component wraps the GitLab UI `chart` component, which in turn wraps the ECharts component.
-
-See the [chart](./?path=/story/charts-chart--default) component for more info.

package/src/components/charts/stacked_column/stacked_column.md

@@ -1,10 +0,0 @@
-The `presentation` property allows you to change between a stacked and tiled presentation style. It
-is only setup to accept `stacked` or `tiled` as values, the default value is `stacked`.
-
-The `stacked` presentation allows to view multiple series of the same stack as a single column,
-while `tiled` presents the information in multiple columns for each series of a stack.
-
-`groupBy` is a property that defines how the data is going to be grouped by for each of the series
-that the `data` property provides. For example if the `data` property has a total of 3 series, with
-7 elements each, `groupBy` could use a 7 element array to show 7 stacked bars or 7 groups of bars
-depending on the preference set by the `presentation` property.

package/src/components/regions/empty_state/empty_state.md

@@ -1,4 +0,0 @@
-### Buttons
-
-You can either have a primary button, a secondary button, or both.
-Buttons require both text a link in order for the button to render.

package/src/components/utilities/animated_number/animated_number.md

@@ -1,6 +0,0 @@
-Animated numbers provide a signifier that values are being changed.
-
-## Usage
-
-The animated number component can be used with or without decimal places. Decimal places will
-not be rounded if chosen to be omitted.

package/src/components/utilities/friendly_wrap/friendly_wrap.md

@@ -1,66 +0,0 @@
-The friendly-wrap component lets you wrap text in a predictable way by appending [`<wbr>`] elements
-to specific break-symbols.
-
-[`<wbr>`]: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/wbr
-
-## Internet Explorer 11
-
-IE11 doesn't support the `<wbr>` element: <https://caniuse.com/#search=wbr>
-To use this component on IE11, you'll need some CSS to preserve its behaviour:
-
-```css
-wbr {
-  display: inline-block;
-}
-```
-
-## Usage
-
-### Default
-
-By default, `GlFriendlyWrap` wraps text with slashes (`/`) as the break-symbol, which is especially
-useful when displaying paths or URLs:
-
-```html
-<gl-friendly-wrap text="/some/file/path" />
-```
-
-The code above renders to the following HTML:
-
-```html
-<span class="text-break">/<wbr>some/<wbr>file/<wbr>path</span>
-```
-
-### Custom symbols
-
-Multiple custom break-symbols can be defined via the `GlFriendlyWrap` prop:
-
-```html
-<gl-friendly-wrap
-  :symbols="[';', '-', '.']"
-  text="some;text-that.needs;to-be.wrapped"
-/>
-```
-
-Which renders to:
-
-```html
-<span class="text-break">some;<wbr>text-<wbr>that.<wbr>needs;<wbr>to-<wbr>be.<wbr>wrapped</span>
-```
-
-### Break words
-
-Symbols can be words too:
-
-```html
-<gl-friendly-wrap
-  :symbols="['and']"
-  text="it goes on and on and on and on"
-/>
-```
-
-Which renders to:
-
-```html
-<span class="text-break">it goes on and<wbr> on and<wbr> on and<wbr> on</span>
-```

package/src/components/utilities/intersection_observer/intersection_observer.md

@@ -1,16 +0,0 @@
-This intersection observer component is an invisible watcher that emits events when it appears and
-dissapears from view.
-
-It acts a a vue-friendly wrapper around the [intersection observer API](https://developer.mozilla.org/en-US/docs/Web/API/Intersection_Observer_API).
-
-Because of it's simplicity you can use it for a lot of different things.
-It's especially helpful for the lazy loading of images, and infinite scrolling of lists.
-
-Anything slotted inside this component will become the element that is being observed.
-
-This slot can also be used as a fallback for the browsers that don't support the intersection
-observer, or in the case that the observer fails to work.
-For example, adding a "Fetch more posts" button inside an observer that should fetch more posts
-automatically when visible. If the observer fails to work for any reason, the button will still be
-clickable, and the experience preserved. Please use a fallback wherever possible as
-**the intersection observer API is not supported in IE11**.

package/src/components/utilities/intersperse/intersperse.md

@@ -1,90 +0,0 @@
-The intersperse component separates a list of elements
-by a given character (the default is `, `).
-
-It takes all direct descendants of its default slot and inserts
-the given separator between each item:
-
-`item 1, item 2, item 3`
-
-Optionally the character used for separating each item and the last separator can be set
-independently:
-
-* `separator="/"`  renders `item 1/item 2/item 3`
-* `lastSeparator=" and "` will render `item 1, item 2, and item 3`
-* `lastSeparator=" and "` and given two items will render `item 1 and item 2`
-
-**Note**:
-
-The component provides an inline context since the result is wrapped in a `span`.
-
-Also, whitespace elements that are direct children of the default-slot get removed to ensure
-consistent formatting.
-
-## Usage
-
-### Default
-
-```html
-<gl-intersperse>
-    <span>Item 1</span>
-    <span>Item 2</span>
-    <span>Item 3</span>
-</gl-intersperse>
-```
-
-This renders to the following HTML:
-
-```html
-<span><span>Item 1</span>, <span>Item 2</span>, <span>Item 3</span></span>
-```
-
-### Custom Separator
-
-A custom separator can be defined via the `separator` prop:
-
-```html
-<gl-intersperse separator="/">
-    <span>Item 1</span>
-    <span>Item 2</span>
-    <span>Item 3</span>
-</gl-intersperse>
-```
-
-This renders to the following HTML:
-
-```html
-<span><span>Item 1</span>/<span>Item 2</span>/<span>Item 3</span></span>
-```
-
-### Custom Last Separator
-
-A custom last separator can be defined via the `lastSeparator` prop:
-
-```html
-<gl-intersperse last-separator=" and ">
-    <span>Item 1</span>
-    <span>Item 2</span>
-    <span>Item 3</span>
-</gl-intersperse>
-```
-
-This renders to the following HTML:
-
-```html
-<span><span>Item 1</span>, <span>Item 2</span>, and <span>Item 3</span></span>
-```
-
-A custom last separator used on two items will only place `lastSeparator` between them:
-
-```html
-<gl-intersperse last-separator=" and ">
-    <span>Item 1</span>
-    <span>Item 2</span>
-</gl-intersperse>
-```
-
-This renders to the following HTML:
-
-```html
-<span><span>Item 1</span> and <span>Item 2</span></span>
-```

package/src/components/utilities/sprintf/sprintf.md

@@ -1,243 +0,0 @@
-## Overview
-
-The `GlSprintf` component lets you do `sprintf`-style string interpolation with
-child components. Each placeholder in the translated string, provided via the
-`message` prop, becomes a slot that you can use to insert any components or
-markup in the rendered output.
-
-> NOTE: `gl-sprintf` does not translate the message for you; you must provide
-> it already translated. In the following examples, it is assumed that
-> a `gettext`-style `__` translation function is available in your Vue
-> templates.
-
-## Displaying messages with text between placeholders (e.g., links, buttons)
-
-Sentences should not be split up into different messages, otherwise they may
-not be translatable into certain languages. To help with this, `GlSprintf`
-interprets placeholders suffixed with `Start` and `End` to indicate the
-boundaries of a component to display within the message. Any text between
-them is passed, via the `content` scoped slot property, to the slot name common
-to the placeholders.
-
-For example, using `linkStart` and `linkEnd` placeholders in a message defines
-a `link` scoped slot:
-
-```html
-<div>
-  <gl-sprintf :message="__('Learn more about %{linkStart}zones%{linkEnd}')">
-    <template #link="{ content }">
-      <gl-link
-        href="https://cloud.google.com/compute/docs/regions-zones/regions-zones"
-        target="_blank"
-      >{{ content }}</gl-link>
-    </template>
-  </gl-sprintf>
-</div>
-```
-
-will render as:
-
-```html
-<div>
-  Learn more about
-  <a
-    href="https://cloud.google.com/compute/docs/regions-zones/regions-zones"
-    target="_blank"
-    rel="noopener noreferrer"
-  >zones</a>
-</div>
-```
-
-Note that _any_ arbitrary HTML tags or Vue component(s) can be used within
-a scoped slot, and that the content passed to it can be used in any way at all;
-for instance, as regular text, or in component attributes or slots.
-
-Here's a more complex example, which `<gl-sprintf>` lets you do in a breeze:
-
-```html
-<div>
-  <gl-sprintf :message="__('Written by %{authorStart}someone%{authorEnd}')">
-    <template #author="{ content }">
-      <my-vue-component v-gl-tooltip="content" @event="handleEvent(content)">
-        {{ content }}
-      </my-vue-component>
-      <p>
-          {{ content }}
-          <div>{{ content }}</div>
-      </p>
-    </template>
-  </gl-sprintf>
-</div>
-```
-
-This is not feasible in a JS-only solution, since arbitrary Vue components
-cannot easily be used. In addition, a JS-only solution is more likely to be
-prone to XSS attacks, as the Vue compiler isn't available to help protect
-against them.
-
-### Customizing start/end placeholders
-
-You can customize the start and end placeholders that `GlSprintf` looks for
-using the `placeholders` prop. For instance:
-
-```html
-<div>
-  <gl-sprintf
-    :message="__('Learn more about %{my_custom_start}zones%{my_custom_end}')"
-    :placeholders="{ link: ['my_custom_start', 'my_custom_end'] }"
-  >
-    <template #link="{ content }">
-      <gl-link
-        href="https://cloud.google.com/compute/docs/regions-zones/regions-zones"
-        target="_blank"
-      >{{ content }}</gl-link>
-    </template>
-  </gl-sprintf>
-</div>
-```
-
-This can be useful if you are migrating an existing string to `GlSprintf` that
-uses different placeholder naming conventions, and don't want invalidate
-existing translations.
-
-## Displaying components within a message
-
-Use slots to replace placeholders in the message with the slots' contents.
-There is a slot for every placeholder in the message. For example, the `author`
-slot name can be used when there is an `%{author}` placeholder in the message:
-
-```html
-<script>
-export default {
-  data() {
-    return {
-      authorName: 'Some author',
-    };
-  },
-};
-</script>
-
-<template>
-  <div>
-    <gl-sprintf :message="__('Written by %{author}')">
-      <template #author>
-        <span>{{ authorName }}</span>
-      </template>
-    </gl-sprintf>
-  </div>
-</template>
-```
-
-The example above renders to this HTML:
-
-```html
-<div>Written by <span>Some author</span></div>
-```
-
-## Usage caveats
-
-### White space
-
-`GlSprintf` does not handle white space in scoped slots specially; it is passed
-through and rendered just like regular text. This means that white space in the
-scoped slot templates _themselves_, including newlines and indentation, are
-passed through untouched (assuming the template compiler you're using doesn't
-trim text nodes at compile time; `vue-template-compiler` preserves white space
-by default, for instance).
-
-Most of the time you don't need to worry about this, since
-[browsers normalize white space][1] automatically, but here's an example, using
-punctuation, where you might want to be conscious of the white space in the
-template:
-
-```html
-<div>
-  <gl-sprintf :message="__('Foo %{boldStart}bar%{boldEnd}!')">
-    <template #bold="{ content }">
-      <b>
-        {{ content }}
-      </b>
-    </template>
-  </gl-sprintf>
-</div>
-```
-
-As written, the literal markup rendered would be:
-
-```html
-<div>  Foo <b>
-        bar
-      </b>!
-</div>
-```
-
-where the white space (including newlines) before and after `bar` is exactly
-the newlines and indentation in the source template. The browser will render
-this as:
-
-<div>  Foo <b>
-        bar
-      </b>!
-</div>
-
-Note the single space between `bar` and `!`. To avoid that, remove the
-white space in the template, or use `v-text`:
-
-```html
-<div>
-  <gl-sprintf :message="__('Foo %{boldStart}bar%{boldEnd}!')">
-    <template #bold="{ content }">
-      <b>{{ content }}</b>
-      <!-- OR -->
-      <b v-text="content" />
-    </template>
-  </gl-sprintf>
-</div>
-```
-
-### Miscellaneous
-
-While there are a lot of caveats here, you don't need to worry about reading
-them _unless_ you find `GlSprintf` isn't rendering what you'd expect.
-
-- Since `GlSprintf` typically renders multiple elements, it can't be used as
-  a component's root, it must be wrapped with at least one other root element,
-  otherwise Vue will throw a `Multiple root nodes returned from render
-  function` error.
-- If a slot for a given placeholder _isn't_ provided, the placeholder
-  will be rendered as-is, e.g., literally `Written by %{author}` if the
-  `author` slot _isn't_ provided, or literally `%{linkStart}foo%{linkEnd}` if
-  the `link` slot isn't provided.
-- Content between `Start` and `End` placeholders is effectively thrown away if
-  the scoped slot of the correct name doesn't consume the `content` property in
-  some way, though the slot's components should still be rendered.
-- If there's no placeholder in the message for a provided named slot, the
-  content of that slot is silently thrown away.
-- If only one of the `Start` or `End` placeholders is in the message, or they
-  are in the wrong order, they are treated as plain slots, i.e., it is assumed
-  there is no text to extract and pass to the scoped slot. This allows you to
-  use plain slots whose names end in `Start` or `End`, e.g., `backEnd`, or
-  `fromStart` in isolation, without their `Start`/`End` counterparts.
-- Text extraction between `Start` and `End` placeholders is only done one level
-  deep. This is intentional, so as to avoid building complex sprintf messages
-  that would better be implemented in components. As an example,
-  `${linkStart}test%{icon}%{linkEnd}`, if provided both the `link` and `icon`
-  slots, would pass `test%{icon}` as a literal string as content to the `link`
-  scoped slot.
-- For more examples and edge cases, please see the test suite for `GlSprintf`.
-- To be successfully used in `GlSprintf`, slot names should:
-  - start with a letter (`[A-Za-z]`)
-  - only contain alpha-numeric characters (`[A-Za-z0-9]`), underscore (`_`) and
-    dash (`-`),
-  - should not end with underscore (`_`) or dash (`-`) So for example:
-    `%{author}`, `%{author_name}`, `%{authorName}` or `%{author-name-100}` are
-    all valid placeholders.
-
-## Internet Explorer 11
-
-This component uses [`String.prototype.startsWith()`] and [`String.prototype.endsWith()`] under the
-hood. Make sure those methods are polyfilled if you plan on using the component on IE11.
-
-[1]: https://www.w3.org/TR/css-text-3/#white-space-phase-1
-[`String.prototype.startsWith()`]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/startsWith
-[`String.prototype.endsWith()`]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/endsWith

package/src/components/utilities/truncate/truncate.md

@@ -1,14 +0,0 @@
-The `GlTruncate` component lets you truncate the long texts with ellipsis.
-
-> **Tip:** Try resizing the side panel for truncation.
-
-## Usage
-
-```html
-<gl-truncate :text="text" :position="position" />
-```
-
-By default, the ellipsis position is at the `end`.
-
-Pro Tip: Truncating long filepaths from the `middle` / `start` can help preventing the important
-information in the end, i.e. filenames.

package/src/components/utilities/truncate_text/truncate_text.md

@@ -1,26 +0,0 @@
-The `GlTruncateText` component lets you truncate a large text by number of lines.
-The last line ends with an ellipsis if the text is truncated.
-Truncation can be toggled by a 'Show more' / 'Show less' button.
-The button will not be shown when no truncation is necessary.
-There is a separate property to set the number of lines initially shown on small screens.
-Use the `showMoreText` and `showLessText` properties to provide translated strings.
-
-> **Tip:** Try resizing the side panel to see the truncated number of lines change.
-
-## Usage
-
-```html
-<gl-truncate-text :show-more-text="__('Show more')" :show-less-text="__('Show less')" :lines="3" :mobile-lines="10">
-  {{ largeText }}
-</gl-truncate-text>
-```
-
-## Usage caveats
-
-When the size of the window is large,
-and the text is displayed on a number of lines greater than the value of the `lines` property,
-but smaller than the value of the `mobileLines` property,
-and the `Show more` button has been clicked to show the entire content of the text,
-and the window is resized to a small size,
-then instead of disappearing,
-the `Show less` button will remain visible and will do nothing when clicked.

package/src/directives/hover_load/hover_load.md

@@ -1,22 +0,0 @@
-A Vue Directive to help with preloading resources when hovering over an element.
-
-## Usage
-
-```html
-<script>
-import { GlHoverLoadDirective } from '@gitlab/ui';
-
-export default {
-  directives: { GlHoverLoadDirective },
-  methods: {
-    handlePreload() {
-      fetch('some/endpoint');
-    },
-  },
-};
-</script>
-
-<template>
-  <div v-gl-hover-load="handlePreload">Hover me to preload</div>
-</template>
-```