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.

Sign up for GitHub

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

Jump to bottom

[Docs] Typo in Scala version of Stream Composition #23588

Closed
arunma opened this issue Sep 2, 2017 · 0 comments
Closed

[Docs] Typo in Scala version of Stream Composition #23588

arunma opened this issue Sep 2, 2017 · 0 comments
Labels
1 - triaged Tickets that are safe to pick up for contributing in terms of likeliness of being accepted help wanted Issues that the core team will likely not have time to work on t:docs
Milestone
2.5.6

Comments

@arunma
Copy link
Contributor

arunma commented Sep 2, 2017

Under Streams -> Modularity, Composition and Hierarchy -> Materialized values,

"This combiner function just ignores the Future[Sink]" must be
"This combiner function just ignores the Future[String]"

The Java version of the document looks fine.
@johanandren johanandren added 1 - triaged Tickets that are safe to pick up for contributing in terms of likeliness of being accepted help wanted Issues that the core team will likely not have time to work on t:docs labels Sep 5, 2017
@johanandren johanandren mentioned this issue Sep 5, 2017
Merged
johanandren pushed a commit that referenced this issue Sep 5, 2017
@arunma @johanandren
Issue #23588 Typo in Scala version of Stream Composition
b4a0521
@johanandren johanandren added this to the 2.5.5 milestone Sep 5, 2017
lucianenache pushed a commit to lucianenache/akka that referenced this issue Nov 6, 2017
@arunma
Issue akka#23588 Typo in Scala version of Stream Composition
d4e8b0b
lucianenache pushed a commit to lucianenache/akka that referenced this issue Nov 9, 2017
@arunma
Issue akka#23588 Typo in Scala version of Stream Composition
cfcef19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
1 - triaged Tickets that are safe to pick up for contributing in terms of likeliness of being accepted help wanted Issues that the core team will likely not have time to work on t:docs
Projects
None yet
Milestone
2.5.6
Development

No branches or pull requests
2 participants
@arunma @johanandren