akka/akka-core

Should we make Merges easier to treat as Sources?

Open

#23,032 opened on May 25, 2017

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Scala (3,547 forks)batch import
1 - triagedhelp wantedt:stream

Repository metrics

Stars
 (13,277 stars)
PR merge metrics
 (Avg merge 8d 19h) (10 merged PRs in 30d)

Description

As mentioned by @QmQvl on gitter: is mergePreferred (http://doc.akka.io/docs/akka/current/scala/stream/stages-overview.html#mergepreferred) not available outside GraphDSL? having to write at least 4-5 lines of ceremonious code is not that much cleaner, arguably 🙃

There is some truth to that - as we know the GraphDSL is the "power user mode", yet already for a MergePreferred people need to drop down to it.

Should we re-consider and make all Merges be usable as "merge these things and give me a source"? I personally think it would be nicer this way, sending in a proposal PR.

Contributor guide

Research direction
Examine current MergePreferred API in GraphDSL and explore how to expose it directly as a Source combinator without requiring GraphDSL ceremony. Propose a simplified API design.
Tech stack
scala
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
ScalaAkka Streams
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35