-
Notifications
You must be signed in to change notification settings - Fork 146
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
protocol Enumerable not implemented for nil #191
Comments
Can you provide more info on the failing spec, such as the spec and any relevant factories? |
I've added a failing test to reproduce this here: https://github.com/thoughtbot/ex_machina/compare/js-nil |
jsteiner
added a commit
that referenced
this issue
Jan 27, 2017
Previously the catchall was falling through to the list case and trying to enumerate `nil`. This commit adds a guard to the list condition to ensure that doesn't happen again, then adds a new condition to handle `nil`. I _think_ this should be handling all cases now, so it also removes the catchall. This way, if it fails in a way we didn't expect, it should give an obvious failure that there was no matching case. Fixes #191
jsteiner
added a commit
that referenced
this issue
Jan 27, 2017
Previously the catchall was falling through to the list case and trying to enumerate `nil`. This commit adds a guard to the list condition to ensure that doesn't happen again, then adds a new condition to handle `nil`. I _think_ this should be handling all cases now, so it also removes the catchall. This way, if it fails in a way we didn't expect, it should give an obvious failure that there was no matching case. Fixes #191
jsteiner
added a commit
that referenced
this issue
Jan 27, 2017
Previously the catchall was falling through to the list case and trying to enumerate `nil`. This commit adds a guard to the list condition to ensure that doesn't happen again, then adds a new condition to handle `nil`. I _think_ this should be handling all cases now, so it also removes the catchall. This way, if it fails in a way we didn't expect, it should give an obvious failure that there was no matching case. Fixes #191
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Using the latest master of this repo (d2d901e), my specs fail with the following error:
Please fix asap.
The text was updated successfully, but these errors were encountered: