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

issue #292 - discard support #293

Merged
merged 4 commits into from
Apr 11, 2023

Conversation

bruto1
Copy link
Contributor

@bruto1 bruto1 commented Feb 14, 2022

please review, @rmichela

@salesforce-cla
Copy link

Thanks for the contribution! Unfortunately we can't verify the commit author(s): Kirill Rodionov <k***@g***.com>. One possible solution is to add that email to your GitHub account. Alternatively you can change your commits to another email and force push the change. After getting your commits associated with your GitHub account, sign the Salesforce.com Contributor License Agreement and this Pull Request will be revalidated.

@bruto1 bruto1 force-pushed the bug/discard-issue-292 branch from 851f581 to 77dabe8 Compare February 14, 2022 15:31
@salesforce-cla
Copy link

Thanks for the contribution! Before we can merge this, we need @bruto1 to sign the Salesforce.com Contributor License Agreement.

@bruto1 bruto1 force-pushed the bug/discard-issue-292 branch from 25eb33d to 0601bfc Compare February 15, 2022 06:08
@bruto1
Copy link
Contributor Author

bruto1 commented Mar 22, 2022

can anyone else take the time to review this, please?
@scottslewis @OlegDokuka

Copy link
Collaborator

@scottslewis scottslewis left a comment

Choose a reason for hiding this comment

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

First, thanks for the pr. These changes and tests appear fine to me.

However, I do not wish to be the only approval for this fix since I'm not at all familiar with this part of the reactive-grpc codebase. I was not involved in the development of reactive-grpc and was recently added as a committer after helping with reactivex 2->3 transition.

@rmichela
Copy link
Collaborator

This looks good. Why wouldn't we implement something similar for RxJava? Is this a Reactor specific issue?

@rmichela
Copy link
Collaborator

@nikolay-pshenichny Can you please take a look?

@bruto1
Copy link
Contributor Author

bruto1 commented Mar 24, 2022

I don't know first thing about RxJava, @rmichela - sry :) Would've changed both impls otherwise

@bruto1
Copy link
Contributor Author

bruto1 commented Aug 11, 2022

@rmichela ?

@rmichela rmichela merged commit 5f3e1be into salesforce:master Apr 11, 2023
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.

3 participants