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

Fixed scan with skip #2357

Merged
merged 3 commits into from
Jan 10, 2019
Merged

Fixed scan with skip #2357

merged 3 commits into from
Jan 10, 2019

Conversation

gamb
Copy link

@gamb gamb commented Jan 7, 2019

Description

Fixes an issue with scan that arose from #2207. The reducer no longer accepted SKIP value as a way of limiting child updates, instead the accumulator value became "SKIP".

For more context see my original change: #1957. The test I added wasn't sufficient to catch breaking change, that is also fixed in this PR! :)

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation change

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.
  • I have updated docs/change-log.md

gamb added 2 commits January 7, 2019 13:30
The previous test didn't catch the fact that the accumulator had been
broke, it's value became the special value `SKIP`.
Copy link
Member

@dead-claudia dead-claudia left a comment

Choose a reason for hiding this comment

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

LGTM mod a nit.

stream/stream.js Outdated Show resolved Hide resolved
Dropped unnecessary ternary as suggested by @isiahmeadows

Co-Authored-By: gamb <[email protected]>
@dead-claudia dead-claudia merged commit 23fe0a5 into MithrilJS:next Jan 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Closed
Development

Successfully merging this pull request may close these issues.

2 participants