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

Commented call to checkIfFailed, to fix submissions bug #59

Merged
merged 17 commits into from
Jul 28, 2018

Conversation

youralien
Copy link
Member

@youralien youralien commented Jul 26, 2018

Summary: Resolves #51 . Future PR (Issue #60) will need to add the functionality that checkIfNeedFailed should have been doing to help with unsuccessful synchronous needs (detailed in the function docs)

Tests: Passes 13/14 tests passing
The only one that fails is

1) Availability Tests update availability:
    AssertionError: user not removed from need2: expected true to be false

In your command line, npm run test or npm run unittest

youralien added 17 commits July 24, 2018 23:56
… operation, to make it possible to write unit tests, and because its only one function that is updating submissions anyway
BUT still failing, with error about
`Error: After filtering out keys not in the schema, your modifier is now
empty` happening in `adminUpdates`
… and tests pass and fail for the stated reasons, instead of some cuz of timing BS
@youralien youralien requested a review from kapil1garg July 28, 2018 00:41
@youralien
Copy link
Member Author

Taking the liberty to close this myself.

@youralien youralien merged commit cb003c8 into master Jul 28, 2018
@youralien youralien deleted the multi-sub-bug branch July 30, 2018 19:14
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.

1 participant