alechenninger / lightblue.js Goto Github PK

With http branch ( #8 ), there is more going on, and the entry points to and division of modules within the library need to be reassessed.

// single, simple projection
var allFields = include("*").recursively();

// include all except some
// multiple projections use array
var exceptSome = [
  include("*").recursively(),
  exclude("some")
];

// array projection
var jsonExampleFromDocs =  [ { "field": "address", "include": true,
     "match": { "city": "Raleigh" }, "project": { "streetaddress": true} } ]

var streetAddressesInRaleigh = include("address")
    .where(field(city).equalTo("Raleigh"))
    .project(include("streetaddress"));

// alternates:
include("streetaddress").in("address").where(field("city").equalTo("Raleigh"));
in("address").where(field("city").equalTo("Raleigh")).include("streetaddress");

Main question is what does it mean in array projection to "include": false?

Doesn't build currently: https://travis-ci.org/alechenninger/lightblue.js/jobs/75752683

The library itself probably works fine, but the tests depend on node.js currently.

For instance, when passing a query, should allow:

• A string of the query expression
• A JSON object of the query expression
• An instance of QueryExpressoin

Basically this would just make it so server-side would not bother with the angular stuff.

Apparently it is not needed anymore

Might be useful to be able to actually test the queries against lightblue, but not sure if it is worth it.

Default to host that served the application

ES6 to ES5 compilers are pretty mature.

Better would be dart's dev_compiler but that sounds like it might be a ways off.

Complete promises with errors as appropriate

Started adding jsdoc throughout, more to do

http://usejsdoc.org/

• Define an interface for an http dependency
• Implement with node http (browserify will wrap XMLHttpRequest)
• Implement with angular $http