Skip to content

1.x: negative argument check for skip's count and merge's maxConcurrent #3677

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

Merged
merged 1 commit into from
Feb 8, 2016

Conversation

zsxwing
Copy link
Member

@zsxwing zsxwing commented Feb 8, 2016

As per #3675, we should also check the count argument of skip. Also added the missing check for merge's maxConcurrent.

@artem-zinnatullin
Copy link
Contributor

I'd suggest to check exception message here and in the other tests, otherwise 👍

@zsxwing
Copy link
Member Author

zsxwing commented Feb 8, 2016

I'd suggest to check exception message here and in the other tests, otherwise

Done

@artem-zinnatullin
Copy link
Contributor

Thanks, @zsxwing! 👍 👍

@akarnokd
Copy link
Member

akarnokd commented Feb 8, 2016

👍

akarnokd added a commit that referenced this pull request Feb 8, 2016
1.x: negative argument check for skip's count and merge's maxConcurrent
@akarnokd akarnokd merged commit ff069cc into ReactiveX:1.x Feb 8, 2016
@zsxwing zsxwing deleted the negative-check branch February 8, 2016 06:31
@stevegury
Copy link
Member

👍

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