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

Support non-binary error-reasons in define_js/4 #35

Merged
merged 1 commit into from
Aug 21, 2013

Conversation

strange
Copy link

@strange strange commented Jan 28, 2013

define_js/4 did not include a pattern to match against non-binary values in
the error tuple that can be a result of evaluating call_driver/4. This caused
case_clause run-time errors when the reason for the error was not a binary.

({error, timeout} for example).

define_js/4 did not include a pattern to match against non-binary values in
the error tuple that can be a result of evaluating call_driver/4. This caused
case_clause run-time errors when the reason for the error was not a binary.

({error, timeout} for example).
@cmeiklejohn
Copy link
Contributor

👍 to merge, https://github.com/basho/erlang_js/blob/master/src/js_driver.erl#L198 is sufficient enough to trigger this condition.

cmeiklejohn added a commit that referenced this pull request Aug 21, 2013
Support non-binary error-reasons in define_js/4
@cmeiklejohn cmeiklejohn merged commit 98f25fc into basho:master Aug 21, 2013
@strange strange deleted the non-binary-errors branch August 27, 2013 13:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants