Skip to content

query-list #12

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

Open
wants to merge 223 commits into
base: master
Choose a base branch
from

Conversation

dmitrys99
Copy link

I've made some lists in my CouchDB instance and done support for it in chillax.
It looks like query-view and works almost the same.

Josh Marchán and others added 30 commits December 29, 2009 20:14
That was pretty retarded of me.
This reverts commit 51216e3.

IT'S USED, DAMNIT!
Josh Marchán and others added 28 commits February 14, 2011 21:06
* Support for the bulk documents API.
* Misc. Fixes.
* Updated and cleaned up documentation.
This version fixes some major breakage with various Chillax components, including views and the
standalone attachment API. There are also some doc updates and miscellaneous tweaks.
This version adds a new server, jsown-server, which uses JSOWN to parse and encode.

JSOWN is meant to be a high-performance JSON library for CL, and may be useful when dealing with
very large objects.
Mostly getting the view server back to work...
@zkat
Copy link
Owner

zkat commented Nov 14, 2012

  • The url-encode issue has already been fixed.
  • The usage pattern for the chillax package does not involve pulling in jsown. The idea of that package is to provide some sane defaults, and if you want more fine-grained control, you should pull in chillax.core and chillax.jsown yourself. I'm not entirely averse to the idea of overloading the chillax package with two json parsers, but my preference is to avoid that.
  • The :include-docs-p change seems reasonable enough.
  • I wish query-view and query-list shared more code. It would be nice to avoid all that copy-paste, even if it involves a common utility function.
  • Could you update the docstrings for the functions you wrote/changed so they follow the documentation patterns in their neighbors?

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.

5 participants