Skip to content
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

feat(forms): add support for tooltip-style feedback text #2188

Merged
merged 26 commits into from
Nov 16, 2018

Conversation

tmorehouse
Copy link
Member

Description of Pull Request:

adds a new boolean prop tooltip to b-form-invalid-feedback, b-form-valid-feedback, and b-form-group that will change the style of feedback from a block of text to a tooltip style.

tooltip style feedback documentation was added to Bootstrap v4.1

PR checklist:

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

  • Bugfix
  • Feature
  • Enhancement to an existing feature
  • ARIA accessibility
  • Documentation update
  • Other, please describe:

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

  • Yes
  • No

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 #xxxx[,#xxxx], where "xxxx" is the issue number)
  • The PR 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.
  • PR titles should following the Conventional Commits naming convention (i.e. "fix(alert): not alerting during SSR render", "docs(badge): Updated pill examples, fix typos", "chore: fix typo in docs", 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)
  • 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 Nov 16, 2018

Codecov Report

Merging #2188 into dev will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##              dev    #2188   +/-   ##
=======================================
  Coverage   65.94%   65.94%           
=======================================
  Files         158      158           
  Lines        3004     3004           
  Branches      836      836           
=======================================
  Hits         1981     1981           
  Misses        741      741           
  Partials      282      282
Impacted Files Coverage Δ
src/components/form/form-invalid-feedback.js 100% <ø> (ø) ⬆️
src/components/form/form-valid-feedback.js 100% <ø> (ø) ⬆️
src/components/form-group/form-group.js 80% <ø> (ø) ⬆️

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 5bdc2e6...a279c45. Read the comment docs.

@tmorehouse tmorehouse merged commit 5203436 into dev Nov 16, 2018
@tmorehouse tmorehouse mentioned this pull request Nov 16, 2018
89 tasks
@tmorehouse tmorehouse deleted the tmorehouse/feedback branch November 17, 2018 02:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant