-
Notifications
You must be signed in to change notification settings - Fork 936
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
reactotron saga -> support yielded promises #346
Comments
Thanks. I've never tried to do that before. |
Thx man. This will be in for the next release shortly. |
joshuayoes
pushed a commit
that referenced
this issue
Jan 17, 2023
Co-authored-by: Renovate Bot <bot@renovateapp.com>
joshuayoes
pushed a commit
that referenced
this issue
Jan 27, 2023
Co-authored-by: Renovate Bot <bot@renovateapp.com>
joshuayoes
pushed a commit
that referenced
this issue
Jan 30, 2023
Co-authored-by: Renovate Bot <bot@renovateapp.com>
joshuayoes
pushed a commit
that referenced
this issue
Feb 1, 2023
Co-authored-by: Renovate Bot <bot@renovateapp.com>
silasjmatson
pushed a commit
that referenced
this issue
Mar 14, 2023
Co-authored-by: Renovate Bot <bot@renovateapp.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently a returned promise - which is supported by redux-saga correctly - reactotron display "UNKNOWN" as entry.
Example:
I consider how it could be more informative.
First "PROMISE" were better than "UNKNOWN".
Maybe if the Promise contains a "name" prop it could take this one. Then display PROMISE(fetchUser).
The text was updated successfully, but these errors were encountered: