Skip to content

chore(plugin): add NAME option to vueUse (closes #3849) #3850

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 7 commits into from
Aug 11, 2019

Conversation

tmorehouse
Copy link
Member

@tmorehouse tmorehouse commented Aug 10, 2019

Describe the PR

Adds an optional NAME property for plugins, which will be set on the window object when using vueUse (if window exists)

Mainly for the browser bundle build, to add in support for both window.bootstrapVue (current) and window.BootstrapVue

Closes #3849

PR checklist

What kind of change does this PR introduce? (check at least one)

  • Bugfix
  • Feature
  • Enhancement
  • ARIA accessibility
  • Documentation update
  • Other (please describe)

Does this PR introduce a breaking change? (check one)

  • No
  • Yes (please describe)

The PR fulfills these requirements:

  • It's submitted to the dev branch, not the master branch
  • When resolving a specific issue, it's referenced in the PR's title (i.e. [...] (fixes #xxx[,#xxx]), where "xxx" is the issue number)
  • It should address only one issue or feature. If adding multiple features or fixing a bug and adding a new feature, break them into separate PRs if at all possible.
  • The title should follow the Conventional Commits naming convention (i.e. fix(alert): not alerting during SSR render, docs(badge): update pill examples, fix typos, chore: fix typo in README, etc). This is very important, as the CHANGELOG is generated from these messages.

If new features/enhancement/fixes are added or changed:

  • Includes documentation updates (including updating the component's package.json for slot and event changes)
  • Includes any needed TypeScript declaration file updates
  • New/updated tests are included and passing (if required)
  • Existing test suites are passing
  • The changes have not impacted the functionality of other components or directives
  • ARIA Accessibility has been taken into consideration (Does it affect screen reader users or keyboard only users? Clickable items should be in the tab index, etc.)

If adding a new feature, or changing the functionality of an existing feature, the PR's
description above includes:

  • A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

@codecov
Copy link

codecov bot commented Aug 10, 2019

Codecov Report

Merging #3850 into dev will increase coverage by <.01%.
The diff coverage is 100%.

Impacted file tree graph

@@           Coverage Diff            @@
##             dev   #3850      +/-   ##
========================================
+ Coverage   99.3%   99.3%   +<.01%     
========================================
  Files        233     233              
  Lines       4452    4453       +1     
  Branches    1262    1262              
========================================
+ Hits        4421    4422       +1     
  Misses        25      25              
  Partials       6       6
Impacted Files Coverage Δ
src/utils/plugins.js 100% <ø> (ø) ⬆️
src/index.js 100% <100%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3c2ea39...bb37850. Read the comment docs.

@tmorehouse tmorehouse changed the title chore(plugin): add NAME option to vueUse chore(plugin): add NAME option to vueUse (closes #3849) Aug 10, 2019
@tmorehouse tmorehouse marked this pull request as ready for review August 10, 2019 22:31
@tmorehouse tmorehouse requested a review from jacobmllr95 August 10, 2019 22:32
@tmorehouse tmorehouse merged commit 8e956e3 into dev Aug 11, 2019
@tmorehouse tmorehouse deleted the tmorehouse/plugin branch August 11, 2019 23:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

BV does not follow Vue global name/function plugin convention
2 participants