Skip to content

Add resolving state to component for multiple instances. #93

New issue

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

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

Already on GitHub? # to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

anant-singh
Copy link

Pushes the resolving state to each instance of a component.

Fixes #90

@codecov
Copy link

codecov bot commented Sep 19, 2018

Codecov Report

Merging #93 into master will increase coverage by 0.26%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master      #93      +/-   ##
==========================================
+ Coverage   92.59%   92.85%   +0.26%     
==========================================
  Files           3        3              
  Lines          81       84       +3     
  Branches       24       24              
==========================================
+ Hits           75       78       +3     
  Misses          6        6
Impacted Files Coverage Δ
src/asyncComponent.js 90.9% <100%> (+0.43%) ⬆️

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 09935a2...97a21e8. Read the comment docs.

@dlebedynskyi
Copy link

@ctrlplusb any change you can get this PR merged? we are blocked by this problem on 2.0 release

@hugofqueiros
Copy link

hi any chance this might be merge?

kronthto added a commit to kronthto/vi0lation.de that referenced this pull request May 9, 2020
Use custom fixed build of async-component with ctrlplusb/react-async-component#93
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Two same simultaneously async components
3 participants