-
Notifications
You must be signed in to change notification settings - Fork 3
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
Improve documentation #89
Conversation
@seancookr @javierg @netlogics @norcal82 This PR's intend is to kick off the documentation improvements, feel free to add commits to this PR. |
@@ -71,8 +71,9 @@ User.all #Dolly::Collection #<#User...>, <#User...> | |||
user = User.find "a1b2d3e" #<#User...> | |||
user.name | |||
|
|||
#Return a User object based on the custom view. | |||
user = User.view 'view_name', {key: ["a", "b", "c"], reduce: true} | |||
#Return a User object based on the custom view. `include_docs` is always true for this method. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is a User
object returned or a json string?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
JSON String, that's why I added the from_json
call, as it previously seemed to indicate you'd be getting a User instead of a String.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Gotcha.
@rubenrails Since no real progress has been made for this, I think we should merge this so as to not let it get stale |
|
DON NOT MERGE...YET
Related #86
This PR aims for improving documentation for the current implementation. DO NOT add/change any functionallity, only documentation changes will be merged.