Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

baucis

Package Overview
Dependencies
Maintainers
1
Versions
202
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

baucis

Module for automatically creating REST interfaces for mongoose schemata

  • 0.3.1-3
  • npm
  • Socket score

Version published
Weekly downloads
20
decreased by-91.27%
Maintainers
1
Weekly downloads
 
Created
Source

baucis v0.3.1-3

Baucis is Express middleware used to build REST services based on Mongoose schemata.

Like Baucis and Philemon of old, this library provides REST to the weary traveler. The goal is to create a JSON REST API for Mongoose & Express that matches as closely as possible the richness and versatility of the HTTP 1.1 protocol.

Those versions published to npm represent release versions. Those versions not published to npm are development releases.

Relase versions of baucis can be considered stable. Baucis uses semver.

Please report issues on GitHub if bugs are encountered.

David Rjckaert III - Philemon and Baucis Giving Hospitality to Jupiter and Mercury

David Rijckaert - Philemon and Baucis Giving Hospitality to Jupiter and Mercury

Usage

To install:

npm install baucis

An example of creating a REST API from a Mongoose schema:

// Define a Mongoose schema
var Vegetable = new mongoose.Schema({
  name: String
});

mongoose.model('vegetable', Vegetable);

// Create routes for the schema
baucis.rest({
  singular: 'vegetable'
});

// Create the app and listen for API requests
var app = express();
app.use('/api/v1', baucis());
app.listen(80);

Later, make requests:

  • GET /api/v1/vegetables/:id — get the addressed document

  • PUT /api/v1/vegetables/:id — create or update the addressed document

  • DEL /api/v1/vegetables/:id — delete the addressed object

  • GET /api/v1/vegetables — get all documents

  • POST /api/v1/vegetables — creates a new document and sends back its ID

  • PUT /api/v1/vegetables — replace all documents with given new documents

  • DEL /api/v1/vegetables — delete all documents

Use plain old Connect/Express middleware, including pre-existing modules like passport. For example, set the all option to add middleware to be called before all the model's API routes.

baucis.rest({
  singular: 'vegetable',
  all: function (request, response, next) {
    if (request.isAuthenticated()) return next();
    return response.send(401);
  }
});

Or, set some middleware for specific HTTP verbs or disable verbs completely:

baucis.rest({
  singular: 'vegetable',
  get: [middleware1, middleware2],
  post: middleware3,
  del: false,
  put: false
});

baucis.rest returns an instance of the controller created to handle the schema's API routes.

var subcontroller = baucis.rest({
  singular: 'bar',
  basePath: '/:fooId/bars'
  publish: false, // don't add API routes automatically
  restrict: function (query, request) {
    // Only retrieve bars that are children of the given foo
    query.where('parent', request.params.fooId);
  }
});

var controller = baucis.rest({
  singular: 'foo',
  configure: function (controller) {
    // Embed the subcontroller at /foos/:fooId/bars
    controller.use(subcontroller);

    // Embed arbitrary middleware at /foos/qux
    controller.use('/qux', function (request, response, next) {
      // Do something cool…
      next();
    });
  }
});

Controllers are Express apps, so do whatever you want with them.

var controller = baucis.rest({
  singular: 'robot',
  configure: function (controller) {
    // Add middleware before all other rotues in the controller
    controller.use(express.cookieParser());
  }
});

// Add middleware after default controller routes
controller.use(function () { ... });
controller.set('some option name', 'value');
controller.listen(3000);

Baucis uses the power of Express, without getting in its way. It's meant to be a way to organize your REST API's Express middleware.

Also note that Mongoose middleware will be executed as usual.

Vegetable.pre('save', function () { ... });

Examples

Examples with jQuery:

$.getJSON('/api/v1/vegetables/4f4028e6e5139bf4e472cca1', function (data) {
  console.log(data);
});

$.ajax({
  type: 'POST',
  dataType: 'json',
  url: '/api/v1/vegetables',
  data: {
    name: 'carrot',
    color: 'orange'
  }
}).done(function (vegetable) {
  // The new document that was just created
  console.dir(vegetable);
});

Requests to the collection (not its members) take standard MongoDB query parameters to filter the documents based on custom criteria.

$.ajax({
  type: 'GET',
  dataType: 'json',
  url: '/api/v1/vegetables',
  data: {
    conditions: JSON.stringify({
      color: 'red',
      'nutrition.sodium': { $lte: 10 }
    })
  }
}).done(function (vegetables) {
  console.dir(vegetables);
});

Examples with Backbone:

var Vegetables = Backbone.Collection.extend({
  url: '/vegetables',
  // This method stringifies baucis' options into fetch's `data` option,
  // while leaving regular fetch options as they are.
  baucis: function (baucisOptions, fetchOptions) {
    fetchOptions = _.clone(fetchOptions || {});
    fetchOptions.data = {};

    if (baucisOptions) {
      Object.keys(baucisOptions).forEach(function (key) {
        fetchOptions.data[key] = JSON.stringify(baucisOptions[key])
      });
    }

    return this.fetch(fetchOptions);
  }
});

var Vegetable = Backbone.Model.extend({
  urlRoot: '/vegetables'
});

var vegetables = new Vegetables();
vegetables.baucis({ conditions: { color: 'red' } }).then( ... );

Besides, the conditions option, populate is also currently supported, to allow population of references to other documents.

var promise = vegetables.baucis({
  conditions: { color: red },
  populate: 'child'
}});

// or

populate: ['child1i', 'child2' ]

// or

populate: [{
  path: 'child1',
  select: ['fieldA', 'fieldB'],
  match: {
    'foo': { $gte: 7 }
  },
  options: { limit: 1 }
}, ... ]

See the Mongoose population documentation for more information.

Contact Info

© 2012-2013 William P. Riley-Land

Keywords

FAQs

Package last updated on 05 May 2013

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc