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

perf(progress): use provide and inject for inter component communication #2540

Merged
merged 2 commits into from Feb 13, 2019

Conversation

tmorehouse
Copy link
Member

Description of Pull Request:

Use provide and inject for better communication between progress and progress-bar

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

If yes, please describe the impact:

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 Feb 12, 2019

Codecov Report

Merging #2540 into dev will decrease coverage by 0.01%.
The diff coverage is 88.88%.

Impacted file tree graph

@@            Coverage Diff             @@
##              dev    #2540      +/-   ##
==========================================
- Coverage   71.47%   71.46%   -0.02%     
==========================================
  Files         172      172              
  Lines        3250     3252       +2     
  Branches      919      919              
==========================================
+ Hits         2323     2324       +1     
- Misses        674      675       +1     
  Partials      253      253
Impacted Files Coverage Δ
src/components/progress/progress.js 100% <100%> (ø) ⬆️
src/components/progress/progress-bar.js 86.36% <87.5%> (-4.12%) ⬇️

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 10fa210...068cdc0. Read the comment docs.

@tmorehouse tmorehouse merged commit 80b7e5f into dev Feb 13, 2019
@tmorehouse tmorehouse deleted the tmorehouse/progress-provide branch February 13, 2019 00:04
@tmorehouse tmorehouse mentioned this pull request Feb 13, 2019
89 tasks
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.

None yet

1 participant