-
Notifications
You must be signed in to change notification settings - Fork 1
AsyncIterator instead of Observable & native async/await for resolve promises #1
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
Open
misak113
wants to merge
17
commits into
master
Choose a base branch
from
next
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
f3d238b to
84bd4c0
Compare
1871a09 to
2381c4e
Compare
…bservables * it would no more needs polyfilling Observable & uses native TS/ES7 language syntax * Refers to https://github.com/tc39/proposal-async-iteration
…erator instead of iterator * it will use asyncIterator even instead of observables for continual side effects * promises are ready to use await instead of yielding promises in updater
b62a7b4 to
c96c25e
Compare
…efix of interface
…ctions are processed
* to allow use modelSaga without redux as middleware
* which are running for longer time until are done * it will not be ran on server-side to prevent special unnecesary calls & to know when request is fullfiled to be rendered & served
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.