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

Possible follow-ups to #830 #844

Closed
3 tasks
simonbasle opened this issue Sep 4, 2017 · 1 comment
Closed
3 tasks

Possible follow-ups to #830 #844

simonbasle opened this issue Sep 4, 2017 · 1 comment
Labels
status/declined We feel we shouldn't currently apply this change/suggestion
Milestone

Comments

@simonbasle
Copy link
Member

simonbasle commented Sep 4, 2017

See #830
- [ ] ignore error when onOperatorError returns null (request 1 more) (superseded by #629)

  • ignore error when onRejectedExecution returns null (request 1 more)
  • update Hooks signature (?)

Possibly separate:

  • add buffered data drop (cancel/error) Operators.onBufferDropped(Collection, Context)
@simonbasle simonbasle added the status/need-decision This needs a decision from the team label Sep 4, 2017
@simonbasle simonbasle added this to the 3.1.0.RELEASE milestone Sep 4, 2017
@smaldini smaldini removed the status/need-decision This needs a decision from the team label Sep 21, 2017
@smaldini smaldini modified the milestones: 3.1.0.RELEASE, 3.2.0.RELEASE Sep 21, 2017
@simonbasle
Copy link
Member Author

closing this as it doesn't seem relevant now that there is doOnDiscard

@simonbasle simonbasle added status/declined We feel we shouldn't currently apply this change/suggestion and removed status/need-investigation This needs more in-depth investigation labels Jun 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/declined We feel we shouldn't currently apply this change/suggestion
Projects
None yet
Development

No branches or pull requests

2 participants