vigetlabs / microcosm

Flux with actions at center stage. Write optimistic updates, cancel requests, and track changes with ease.
http://code.viget.com/microcosm/
MIT License
487 stars 22 forks source link

Ch/design tweak test #459

Closed ccchwang closed 6 years ago

ccchwang commented 6 years ago

What kind of change does this PR introduce?

Does this PR introduce a breaking change?

If yes, please describe the impact and migration path for existing applications:

Does this PR fulfill these requirements:

Additional Information

codecov-io commented 6 years ago

Codecov Report

Merging #459 into master will decrease coverage by 19.51%. The diff coverage is 100%.

Impacted file tree graph

@@             Coverage Diff             @@
##           master     #459       +/-   ##
===========================================
- Coverage   93.19%   73.68%   -19.52%     
===========================================
  Files          29       44       +15     
  Lines        1029     1368      +339     
  Branches      197      255       +58     
===========================================
+ Hits          959     1008       +49     
- Misses         59      295      +236     
- Partials       11       65       +54
Impacted Files Coverage Δ
packages/microcosm/src/utils.js 100% <ø> (+1.36%) :arrow_up:
packages/microcosm/src/action.js 100% <100%> (+3.41%) :arrow_up:
packages/microcosm/src/coroutine.js 100% <100%> (+56%) :arrow_up:
packages/microcosm/src/addons/action-form.js 97.61% <100%> (ø)
packages/microcosm/src/addons/indexing.js 0% <0%> (-100%) :arrow_down:
packages/microcosm/src/addons/action-queue.js 0% <0%> (-80%) :arrow_down:
packages/microcosm-preact/test/helpers.js
packages/microcosm-preact/test/setup.js
packages/microcosm-graphql/src/repo.js 0% <0%> (ø)
packages/microcosm-graphql/src/errors.js 0% <0%> (ø)
... and 23 more

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 25a2764...94e8983. Read the comment docs.