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

Update decorator method to accept meta and options #71

Merged
merged 2 commits into from Apr 4, 2017

Conversation

pkat
Copy link
Contributor

@pkat pkat commented Oct 27, 2016

Currently Calibrate.response allows for 3 parameters for data, meta and options. However using the decorator method does not allow for the additional information (meta and options). Is there a reason that its not included? This PR updates the method to accept those params.

Currently `Calibrate.response` allows for 3 parameters for data, meta and options. However using the decorator method does not allow for the additional information (meta and options). Is there a reason that its not included? This PR updates the method to accept those params.
@coveralls
Copy link

coveralls commented Oct 27, 2016

Coverage Status

Coverage remained the same at 100.0% when pulling 62f5ed1 on pkat:patch-1 into 6e0cb29 on johnbrett:master.

@coveralls
Copy link

coveralls commented Oct 27, 2016

Coverage Status

Coverage remained the same at 100.0% when pulling 6c1cf4d on pkat:patch-1 into 6e0cb29 on johnbrett:master.

Copy link
Collaborator

@AdrieanKhisbe AdrieanKhisbe left a comment

Choose a reason for hiding this comment

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

I don't see no specific reason to do so

@johnbrett
Copy link
Owner

@AdrieanKhisbe your double negative has confused me :) You mean to don't see any reason why we should pass meta / options, or you don't see any reason why not to? :)

@AdrieanKhisbe
Copy link
Collaborator

haha. I don't see any reason why we shouldn't had them.

@johnbrett
Copy link
Owner

Agreed, likely an oversight on my part. Also - @pkat I did not see this until now!! October 27!! So sorry for the late reply!!!

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.

None yet

4 participants