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

fix(Effects): Start child effects after running root effects #43

Merged
merged 1 commit into from
Jun 20, 2017

Conversation

MikeRyanDev
Copy link
Member

This removes the app initialization logic altogether. The 'OnRunEffects'
lifecycle hook should be sufficient to control when your effects start.

cc @robwormald

Closes #37

@MikeRyanDev MikeRyanDev force-pushed the fix/run-effects-on-initialization branch from 4414e62 to e89140f Compare June 20, 2017 13:55
@brandonroberts
Copy link
Member

LGTM

This removes the app initialization logic altogether. The 'OnRunEffects'
lifecycle hook should be sufficient to control when your effects start.
@MikeRyanDev MikeRyanDev force-pushed the fix/run-effects-on-initialization branch from e89140f to 7a7861b Compare June 20, 2017 14:01
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.05%) to 88.419% when pulling 7a7861b on fix/run-effects-on-initialization into 0be1bee on master.

@brandonroberts brandonroberts merged commit 931adb1 into master Jun 20, 2017
@brandonroberts brandonroberts deleted the fix/run-effects-on-initialization branch June 20, 2017 17:04
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.

3 participants