Merge branch 'dev' into readme-partners

jacobmllr95 · web-flow · commit e79251ab57da · 2020-04-29T09:28:20.000+02:00
diff --git a/docs/components/contributors.vue b/docs/components/contributors.vue
@@ -236,7 +236,7 @@ export default {
           imageUrl: entry.fromAccount.imageUrl,
           // We only link their website when the total amount is at or above a certain
           // threshold to prevent some questionable websites from abusing opencollective
-          // as a means to improve thier Google page ranking via backlinks
+          // as a means to improve their Google page ranking via backlinks
           website:
             Math.max(amount || 0, totalAmount || 0) < LINK_AMT_THRESHOLD
               ? null
diff --git a/docs/pages/themes.vue b/docs/pages/themes.vue
@@ -71,8 +71,8 @@
             vendor/provider website for current pricing.
           </li>
           <li>
-            Theme licenses are typicaly per-site (unless onterwised noted). Refer to the theme site
-            documentaton for licensing information.
+            Theme licenses are typically per-site (unless onterwised noted). Refer to the theme
+            site documentation for licensing information.
           </li>
           <li>
             BootstrapVue does not guarantee that all coustom components provided by a theme are
@@ -102,10 +102,10 @@
           </li>
           <li>
             Should avoid the need for jQuery or Bootstrap v4 JavaScript files (except for included
-            3<sup>rd</sup> party compoents if required).
+            3<sup>rd</sup> party components if required).
           </li>
           <li>Should provide the source SCSS/SASS files/variables.</li>
-          <li>Should promote that it is based on (or compatable with) <i>BootstrapVue</i>.</li>
+          <li>Should promote that it is based on (or compatible with) <i>BootstrapVue</i>.</li>
           <li>
             Custom components provided by the theme should be WAI-ARIA accessible. Any WAI-ARIA
             limitations should be noted in the theme documeantation.
diff --git a/package.json b/package.json
@@ -111,7 +111,7 @@
     "autoprefixer": "^9.7.6",
     "babel-core": "^7.0.0-bridge.0",
     "babel-eslint": "^10.1.0",
-    "babel-jest": "^25.4.0",
+    "babel-jest": "^25.5.0",
     "babel-plugin-istanbul": "^6.0.0",
     "bootstrap-icons": "^1.0.0-alpha3",
     "bundlewatch": "^0.2.6",
@@ -138,9 +138,9 @@
     "html-loader": "^1.1.0",
     "husky": "^4.2.5",
     "improved-yarn-audit": "^2.0.0",
-    "jest": "^25.4.0",
+    "jest": "^25.5.0",
     "jest-environment-jsdom-fourteen": "^1.0.1",
-    "lint-staged": "^10.1.7",
+    "lint-staged": "^10.2.0",
     "loader-utils": "^2.0.0",
     "lodash": "^4.17.15",
     "marked": "^1.0.0",
diff --git a/src/components/avatar/README.md b/src/components/avatar/README.md
@@ -61,7 +61,7 @@ styling on the content.
 
 Use the `src` prop to specify a URL of an image to use as the avatar content. The image should have
 an aspect ratio of `1:1` (meaning the width and height should be equal), otherwise image aspect
-distortion will occur. The image will be scaled up or down to fit withing the avatar's bounding box,
+distortion will occur. The image will be scaled up or down to fit within the avatar's bounding box,
 and will be sized to show the avatar's [variant background](#variants) around the edge.
 
 ```html
diff --git a/src/components/calendar/calendar.js b/src/components/calendar/calendar.js
@@ -370,7 +370,7 @@ export const BCalendar = Vue.extend({
     },
     // Computed props that return a function reference
     dateOutOfRange() {
-      // Check wether a date is within the min/max range
+      // Check whether a date is within the min/max range
       // returns a new function ref if the pops change
       // We do this as we need to trigger the calendar computed prop
       // to update when these props update
diff --git a/src/components/card/card-img-lazy.spec.js b/src/components/card/card-img-lazy.spec.js
@@ -141,7 +141,7 @@ describe('card-image', () => {
     expect(wrapper.attributes('width')).toBe('600')
   })
 
-  it('has attribute heigth when prop height set', async () => {
+  it('has attribute height when prop height set', async () => {
     const wrapper = mount(BCardImgLazy, {
       context: {
         props: {
diff --git a/src/components/card/card-img.spec.js b/src/components/card/card-img.spec.js
@@ -141,7 +141,7 @@ describe('card-image', () => {
     expect(wrapper.attributes('width')).toBe('600')
   })
 
-  it('has attribute heigth when prop height set', async () => {
+  it('has attribute height when prop height set', async () => {
     const wrapper = mount(BCardImg, {
       context: {
         props: {
diff --git a/src/components/form-datepicker/README.md b/src/components/form-datepicker/README.md
@@ -520,7 +520,7 @@ Internationalization of the date picker's calendar is provided via
 [`Intl.DateTimeFormat`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/DateTimeFormat),
 except for labels applied to elements of the calendar control (aria-labels, selected status, and
 help text). You must provide your own translations for these labels. The available locales will be
-browser dependant (not all browsers support all locales)
+browser dependent (not all browsers support all locales)
 
 By default `<b-form-datepicker>` will use the browser's default locale, but you can specify the
 locale (or locales) to use via the `locale` prop. The prop accepts either a single locale string, or
diff --git a/src/components/form-rating/README.md b/src/components/form-rating/README.md
@@ -473,7 +473,7 @@ The following is an example of placing `<b-form-rating>` in an input group:
 
 When a `locale` is specified, the displayed value (when the `show-value` prop is `true`) will be in
 the browser's default locale. To change the locale, simple set the `locale` prop to the preferred
-locale, or an array of prefered locales (most preferred locale first). This will affect the optional
+locale, or an array of preferred locales (most preferred locale first). This will affect the optional
 displayed value and the left-to-right or right-to-left orientation of the component.
 
 ```html
diff --git a/src/components/form-spinbutton/README.md b/src/components/form-spinbutton/README.md
@@ -202,7 +202,7 @@ By default `<b-form-spinbutton>` will format the displayed number in the users b
 locale. You can change the localized formatting by specifying a locale (or array of locales) via the
 `locale` prop. Number format localization is performed via
 [`Intl.NumberFormat`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/NumberFormat).
-The locales available will be dependant on the browser implementation. Localization only controls
+The locales available will be dependent on the browser implementation. Localization only controls
 the presentation of the value to the user, and does not affect the `v-model`.
 
 ```html
diff --git a/src/components/form-timepicker/README.md b/src/components/form-timepicker/README.md
@@ -269,11 +269,11 @@ and
 [`Intl.NumberFormat`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/NumberFormat),
 except for the labels applied to elements of the time control (aria-labels, selected status, etc).
 You must provide your own translations for these labels. The available locales will be browser
-dependant (not all browsers support all locales).
+dependent (not all browsers support all locales).
 
 By default `<b-form-timepicker>` will use the browser's default locale, but you can specify the
 locale (or locales) to use via the `locale` prop. The prop accepts either a single locale string, or
-an array of locale strings (listed in order of most preferred locale to least prefered).
+an array of locale strings (listed in order of most preferred locale to least preferred).
 
 The emitted `'context'` event will include which locale the time control has resolved to (which may
 not be the same locale as requested, depending on the supported locales of `Intl`).
@@ -389,7 +389,7 @@ presented/formatted to a user of a particular locale. The `'context'` event incl
 Native HTML5 `<input type="date">` returns the time value in the `'h23'` format, and
 `<b-form-timepicker>` also returns the v-model in the `'h23'` format. This value may differ from
 what is presented to the user via the GUI (spin buttons) of the `<b-form-timepicker>` component,
-dependant upon the [locale selected](#internationalization).
+dependent upon the [locale selected](#internationalization).
 
 **Note:** IE 11 _does not support_ resolving the `hourCycle` value of a locale, so we assume either
 `h12` or `h23` based on the resolved `hour12` value.
diff --git a/src/components/form-timepicker/form-timepicker.js b/src/components/form-timepicker/form-timepicker.js
@@ -357,7 +357,7 @@ export const BFormTimepicker = /*#__PURE__*/ Vue.extend({
 
     if (this.resetButton) {
       if ($footer.length > 0) {
-        // Add a "spacer" betwen buttons ('&nbsp;')
+        // Add a "spacer" between buttons ('&nbsp;')
         $footer.push(h('span', '\u00a0'))
       }
       const label = this.labelResetButton
@@ -377,7 +377,7 @@ export const BFormTimepicker = /*#__PURE__*/ Vue.extend({
 
     if (!this.noCloseButton) {
       if ($footer.length > 0) {
-        // Add a "spacer" betwen buttons ('&nbsp;')
+        // Add a "spacer" between buttons ('&nbsp;')
         $footer.push(h('span', '\u00a0'))
       }
       const label = this.labelCloseButton
diff --git a/src/components/modal/modal.spec.js b/src/components/modal/modal.spec.js
@@ -1013,7 +1013,7 @@ describe('modal', () => {
 
       expect($modal.element.style.display).toEqual('block')
 
-      // Simulate an other modal opening (by emiting a fake BvEvent)
+      // Simulate an other modal opening (by emitting a fake BvEvent)
       // `bvEvent.vueTarget` is normally a Vue instance, but in this
       // case we just use a random object since we are checking inequality
       wrapper.vm.$root.$emit('bv::modal::show', { vueTarget: Number })
diff --git a/src/components/popover/README.md b/src/components/popover/README.md
@@ -150,7 +150,7 @@ Positioning is relative to the trigger element.
   <div class="clearfix"></div>
 </div>
 
-Refer to the [Popover directive](/docs/directives/popover/#positioning) documentaion for live
+Refer to the [Popover directive](/docs/directives/popover/#positioning) documentation for live
 examples of positioning.
 
 ## Triggers
diff --git a/src/components/sidebar/README.md b/src/components/sidebar/README.md
@@ -302,7 +302,7 @@ elements outside of the sidebar.
 
 ### `v-b-toggle` directive
 
-Using the `v-b-toggle` directive is the prefered method for _opening_ the sidebar, as it
+Using the `v-b-toggle` directive is the preferred method for _opening_ the sidebar, as it
 automatically handles applying the `aria-controls` and `aria-expanded` accessibility attributes on
 the trigger element.
 
diff --git a/src/components/table/README.md b/src/components/table/README.md
@@ -2159,7 +2159,7 @@ If you have a text input tied to the `filter` prop of `<b-table>`, the filtering
 for each character typed by the user. With large items datasets, this process can take a while and
 may cause the text input to appear sluggish.
 
-To help alleviate this type of situation, `<b-table>` accepts a debounce timout value (in
+To help alleviate this type of situation, `<b-table>` accepts a debounce timeout value (in
 milliseconds) via the `filter-debounce` prop. The default is `0` (milliseconds). When a value
 greater than `0` is provided, the filter will wait for that time before updating the table results.
 If the value of the `filter` prop changes before this timeout expires, the filtering will be once
diff --git a/src/components/table/_table.scss b/src/components/table/_table.scss
@@ -113,7 +113,7 @@
   }
 
   @media print {
-    // Overide any styles (including inline styles)
+    // Override any styles (including inline styles)
     // when printing
     .b-table-sticky-header {
       overflow-y: visible !important;
diff --git a/src/components/table/helpers/mixin-thead.js b/src/components/table/helpers/mixin-thead.js
@@ -146,7 +146,7 @@ export default {
       // Generate the array of <th> cells
       const $cells = fields.map(makeCell).filter(identity)
 
-      // Genrate the row(s)
+      // Generate the row(s)
       const $trs = []
       if (isFoot) {
         const trProps = {
diff --git a/src/components/table/table-filtering.spec.js b/src/components/table/table-filtering.spec.js
@@ -238,7 +238,7 @@ describe('table > filtering', () => {
 
   describe('debouncing (deprecated)', () => {
     // Wrapped in a describe to limit console.warn override
-    // to prevent depreacted prop warnings
+    // to prevent deprecated prop warnings
     const originalWarn = console.warn
     afterEach(() => (console.warn = originalWarn))
     beforeEach(() => (console.warn = () => {}))
diff --git a/src/components/table/table-sorting.spec.js b/src/components/table/table-sorting.spec.js
@@ -770,7 +770,7 @@ describe('table > sorting', () => {
     wrapper.destroy()
   })
 
-  it('sorting by virutal column formatter works', async () => {
+  it('sorting by virtual column formatter works', async () => {
     const wrapper = mount(BTable, {
       propsData: {
         items: [{ a: 5, b: 2 }, { a: 10, b: 9 }],
diff --git a/src/components/time/README.md b/src/components/time/README.md
@@ -242,11 +242,11 @@ and
 [`Intl.NumberFormat`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/NumberFormat),
 except for the labels applied to elements of the time control (aria-labels, selected status, etc).
 You must provide your own translations for these labels. The available locales will be browser
-dependant (not all browsers support all locales).
+dependent (not all browsers support all locales).
 
 By default `<b-time>` will use the browser's default locale, but you can specify the locale (or
 locales) to use via the `locale` prop. The prop accepts either a single locale string, or an array
-of locale strings (listed in order of most preferred locale to least prefered).
+of locale strings (listed in order of most preferred locale to least preferred).
 
 The emitted `'context'` event will include which locale the time control has resolved to (which may
 not be the same locale as requested, depending on the supported locales of `Intl`).
@@ -358,7 +358,7 @@ includes the resolved `hourCycle` value.
 
 Native HTML5 `<input type="date">` returns the time value in the `'h23'` format, and `<b-time>` also
 returns the v-model in the `'h23'` format. This value may differ from what is presented to the user
-via the GUI (spin buttons) of the `<b-time>` component, dependant upon the
+via the GUI (spin buttons) of the `<b-time>` component, dependent upon the
 [locale selected](#internationalization).
 
 **Note:** IE 11 _does not support_ resolving the `hourCycle` value of a locale, so we assume either
diff --git a/src/components/toast/README.md b/src/components/toast/README.md
@@ -580,7 +580,7 @@ provides general guidelines when using toasts.
   be reached by keyboard-only users.
 - Avoid initiating many toasts in quick succession, as screen readers may interrupt reading the
   current toast and announce the new toast, causing the context of the previous toast to be missed.
-- For toasts with long textual content, adjust the `auto-hide-delay` to a larger timout, to allow
+- For toasts with long textual content, adjust the `auto-hide-delay` to a larger timeout, to allow
   users time to read the content of the toast. A good length of time to keep messages up is 4
   seconds plus 1 extra second for every 100 words, rounding up. This is approximately how fast the
   average person reads. That means the shortest default that should be used as a best practice is 5
diff --git a/src/components/tooltip/README.md b/src/components/tooltip/README.md
@@ -96,7 +96,7 @@ The default position is `top`. Positioning is relative to the trigger element.
   </div>
 </div>
 
-Refer to the [Tooltip directive](/docs/directives/tooltip/#positioning) documentaion for live
+Refer to the [Tooltip directive](/docs/directives/tooltip/#positioning) documentation for live
 examples of positioning.
 
 ## Triggers
@@ -210,7 +210,7 @@ override the `pointer-events` on the disabled element.
 | `container`          | `null`           | Element string ID to append rendered tooltip into. If `null` or element not found, tooltip is appended to `<body>` (default)                                                                               | Any valid in-document unique element ID.                                                                                                         |
 | `boundary`           | `'scrollParent'` | The container that the tooltip will be constrained visually. The default should suffice in most cases, but you may need to change this if your target element is in a small container with overflow scroll | `'scrollParent'` (default), `'viewport'`, `'window'`, or a reference to an HTML element.                                                         |
 | `boundary-padding`   | `5`              | Amount of pixel used to define a minimum distance between the boundaries and the tooltip. This makes sure the tooltip always has a little padding between the edges of its container                       | Any positive number                                                                                                                              |
-| `noninteractive`     | `false`          | Wether the tooltip should not be user-interactive                                                                                                                                                          | `true` or `false`                                                                                                                                |
+| `noninteractive`     | `false`          | Whether the tooltip should not be user-interactive                                                                                                                                                          | `true` or `false`                                                                                                                                |
 | `variant`            | `null`           | Contextual color variant for the tooltip                                                                                                                                                                   | Any contextual theme color variant name                                                                                                          |
 | `custom-class`       | `null`           | A custom classname to apply to the tooltip outer wrapper element                                                                                                                                           | A string                                                                                                                                         |
 | `id`                 | `null`           | An ID to use on the tooltip root element. If none is provided, one will automatically be generated. If you do provide an ID, it _must_ be guaranteed to be unique on the rendered page                     | A valid unique element ID string                                                                                                                 |
@@ -404,7 +404,7 @@ long as you have provided the `.sync` prop modifier.
 ```
 
 **Note:** _In the above example, since we are using the default tooltip triggers of `focus hover`,
-the tooltip will close before it is disabled due to loosing focus (and hover) to the toggle button._
+the tooltip will close before it is disabled due to losing focus (and hover) to the toggle button._
 
 You can also emit `$root` events to trigger disabling and enabling of tooltip(s). See the
 **Disabling and enabling tooltips via \$root events** section below for details.
diff --git a/src/components/tooltip/helpers/bv-tooltip.js b/src/components/tooltip/helpers/bv-tooltip.js
@@ -771,7 +771,7 @@ export const BVTooltip = /*#__PURE__*/ Vue.extend({
         this.enter(evt)
       } else if (type === 'focusin' && arrayIncludes(triggers, 'focus')) {
         // `focusin` is a bubbling event
-        // `evt` includes `relatedTarget` (element loosing focus)
+        // `evt` includes `relatedTarget` (element losing focus)
         this.enter(evt)
       } else if (
         (type === 'focusout' &&
@@ -782,7 +782,7 @@ export const BVTooltip = /*#__PURE__*/ Vue.extend({
         // `mouseleave` is a non-bubbling event
         // `tip` is the template (will be null if not open)
         const tip = this.getTemplateElement()
-        // `evtTarget` is the element which is loosing focus/hover and
+        // `evtTarget` is the element which is losing focus/hover and
         const evtTarget = evt.target
         // `relatedTarget` is the element gaining focus/hover
         const relatedTarget = evt.relatedTarget
diff --git a/src/directives/tooltip/README.md b/src/directives/tooltip/README.md
diff --git a/src/mixins/dropdown.js b/src/mixins/dropdown.js
diff --git a/src/mixins/form-text.js b/src/mixins/form-text.js
diff --git a/src/mixins/has-listener.js b/src/mixins/has-listener.js
diff --git a/src/utils/bv-collapse.js b/src/utils/bv-collapse.js
diff --git a/src/utils/config-defaults.js b/src/utils/config-defaults.js
diff --git a/src/utils/observe-dom.js b/src/utils/observe-dom.js
diff --git a/yarn.lock b/yarn.lock
