-
Notifications
You must be signed in to change notification settings - Fork 5
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
Diagram explaining flow #1
Comments
Yes, I think that would be helpful to better illustrate the intended flow. Also, after going through this if you have thoughts on changes to the api, method names, etc, it would be great to hear them. I think renaming some things list |
I think once there's a diagram, complexities will be much easier to spot (pun intended 😉) (One api change that comes to my mind is to make stream a getter that automatically calls Just one thing I can't get my head around: How should I display partially reading from a source and then re-using it in the diagram? |
Currently trying to make sense of this using diagrams.
(Isn't finished yet -
rest()
and.stream
are missing)I think it would be a good idea to have some kind of "diagram" like that one for every stream module, to get a better understanding of what these streams actually do
Thoughts?
The text was updated successfully, but these errors were encountered: