Skip to content

Conversation

@david-driscoll
Copy link
Contributor

When the OperationExecutor does not emit any error results, because the Result is always null.

I was not sure how best to fix this, and I'm not as deeply involved in the spec, so this is my best guess atm.
Basically if any error results are found, OperationExecutor will OnNext and complete the observable. This could be wrong behavior instead of just OnNext the result and move on.

I made the change to both OperationExecutor and StorelessOperationExecutor so their behavior would be consistent. (And to help identify if I'm thinking about errors all the wrong way).

@michaelstaib
Copy link
Member

@david-driscoll thanks for contributing this ... I will package it into 14.1

@michaelstaib
Copy link
Member

OK ... I will need to look into why the tests fail.

@david-driscoll
Copy link
Contributor Author

I missed those tests myself, I'll try and take a look as well.

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.

2 participants