GithubHelp home page GithubHelp logo

mattetti / couchrest Goto Github PK

View Code? Open in Web Editor NEW

This project forked from jchris/couchrest

81.0 2.0 13.0 3.57 MB

A RESTful CouchDB client based on Heroku's RestClient and Couch.js

Home Page: http://jchris.lighthouseapp.com/projects/17807-couchrest/overview

couchrest's Introduction

couchrest's People

Contributors

adamhjk avatar antonyblakey avatar candlerb avatar deepj avatar gbuesing avatar igal avatar jchris avatar kirel avatar mattetti avatar nanodeath avatar ndarilek avatar orangewolf avatar quirkey avatar rafaelss avatar ratbeard avatar roidrage avatar sporkd avatar tapajos avatar tc avatar topfunky avatar viniciusteles avatar wagenet avatar wasnotrice avatar wildchild avatar will avatar yohei avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar

couchrest's Issues

Couchrest-type should be changed to couchrest_type in docs

Hi,
I think it should be changed and respected Ruby and ECMA-262 identifier conventions. For example timestamps! use _ instead of - (created_at instead of created-at). Is there any special reason for using couchrest-type instead of couchrest_type?

For example then I can use this way in map function:

function(doc) {
if (doc.couchrest_type == 'Document') {
....
}
}

http://github.com/deepj/couchrest/commit/439aa3bae502f5ca0155185a2eaddcc0203aadbf

Model.create doesn't work

There seem to be a bug with the create class method. Instead, the method is defined on instances. Model.new.create({}) would probably currently work.

Model.new(@x) wipes @x

Hi, is this intended?

>> @va = {:user_id => 10}
=> {:user_id=>10}
>> r = Rwatch.new(@va)
=> {"user_id"=>10, "couchrest-type"=>"Rwatch"}
>> @va
=> {}

-- Frank

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.