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.

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

2.x: add Flowable.doAfterNext operator + 3 doX TCKs #4833

Merged
merged 2 commits into from Nov 11, 2016

Conversation

akarnokd
Copy link
Member

This PR adds the Flowable.doAfterNext operator which calls a Consumer after the call to downstream.onNext() with the same value.

In addition, doOnNext, doAfterNext and doFinally received their Reactive-Streams TCK tests.

@akarnokd akarnokd added this to the 2.1 milestone Nov 10, 2016
@codecov-io
Copy link

codecov-io commented Nov 10, 2016

Current coverage is 95.73% (diff: 100%)

Merging #4833 into 2.x will increase coverage by 0.02%

@@                2.x      #4833   diff @@
==========================================
  Files           576        577     +1   
  Lines         37048      37093    +45   
  Methods           0          0          
  Messages          0          0          
  Branches       5591       5596     +5   
==========================================
+ Hits          35459      35512    +53   
+ Misses          660        654     -6   
+ Partials        929        927     -2   

Powered by Codecov. Last update 2f8e8bc...32becbf

@Override
public Publisher<Integer> createPublisher(long elements) {
return FlowableTck.wrap(
Flowable.range(0, (int)elements).doOnNext(Functions.emptyConsumer())
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't really understand the purpose of these three tests. If the side-effecting operator just swallows the event it's not really validating anything.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These test verify that the operators and the chain still honors the RS specification. The regular JUnit test verify if the operator does what it supposed to do.

@akarnokd akarnokd merged commit 715d71d into ReactiveX:2.x Nov 11, 2016
@akarnokd akarnokd deleted the FlowableDoAfterNext branch November 11, 2016 08:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants