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

Allowing CosmosPageFlux.handle consumers to get chained #20040

Conversation

FabianMeiswinkel
Copy link
Member

No description provided.

Copy link
Contributor

@moderakh moderakh left a comment

Choose a reason for hiding this comment

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

signing off on this one

but a a rule of thumb,
For any improvement we do for the core SDK on the feature/cosmos/spark30 branch, if it is not urgent can we leave the porting for later. When the feature branch merges back to the master all the improvements will come to master naturally.

my concern is to reduce unnecessary merge conflicts for back and forth merging of master to the feature branch or feature branch to the master.

Copy link
Member

@kushagraThapar kushagraThapar left a comment

Choose a reason for hiding this comment

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

LGTM

@FabianMeiswinkel FabianMeiswinkel merged commit 9554519 into Azure:master Mar 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants