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

Bringing back the commit that was lost because of bad merge. #2122

Conversation

hjafarpour
Copy link
Contributor

This is a commit that was lost because of a bad merge. Bringing it back in this PR.

@hjafarpour hjafarpour requested a review from a team as a code owner November 6, 2018 04:27
@hjafarpour hjafarpour changed the title BRinging back the commit that was lost because of bad merge. Bringing back the commit that was lost because of bad merge. Nov 6, 2018
@framiere
Copy link

framiere commented Nov 6, 2018

Have you considered using a supplier in the orElse method ?

@apurvam
Copy link
Contributor

apurvam commented Nov 6, 2018

@framiere yes, that was the suggestion on the original PR. Since this is cherry picking the original patch, it is unchanged. I agree that using the supplier form of orElse is the right thing to do, but not in this patch.

Copy link
Contributor

@apurvam apurvam left a comment

Choose a reason for hiding this comment

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

LGTM, thanks!

Copy link
Contributor

@rodesai rodesai left a comment

Choose a reason for hiding this comment

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

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants