项目作者: Prasanna-sr

项目描述 :
Node.js module provides versioning for expressjs routes/api
高级语言: JavaScript
项目地址: git://github.com/Prasanna-sr/express-routes-versioning.git
创建时间: 2016-02-20T09:18:22Z
项目社区:https://github.com/Prasanna-sr/express-routes-versioning

开源协议:MIT License

下载


Express routes versioning

Build Status Coverage Status
npm version

Simple node.js module provides versioning for expressjs routes/api.

Install

npm install express-routes-versioning

Usage

Follows semver versioning format. Supports ‘^, ~’ symbols for matching version numbers.

  1. var app = require('express')();
  2. var routesVersioning = require('express-routes-versioning')();
  3. app.listen(3000);
  4. app.get('/test', routesVersioning({
  5. "1.0.0": respondV1,
  6. "~2.2.1": respondV2
  7. }));
  8. // curl -s -H 'accept-version: 1.0.0' localhost:3000/test
  9. // version 1.0.0 or 1.0 or 1 !
  10. function respondV1(req, res, next) {
  11. res.status(200).send('ok v1');
  12. }
  13. //curl -s -H 'accept-version: 2.2.0' localhost:3000/test
  14. //Anything from 2.2.0 to 2.2.9
  15. function respondV2(req, res, next) {
  16. res.status(200).send('ok v2');
  17. }

Supporting ‘^,~’ on server might appear as an anti-pattern considering how npm versioning works, where client controls the version. Here server controls the version (or it may not), and client fully trust the server. Typically the client and server belong to the same organization in these cases.

API

routesVersioning(Options, NoMatchFoundCallback)

Options - object, containing version in semver format (supports ^,~ symbols) as key and function callback (connect middleware format) to invoke when the request matches the version as value. Note: Versions are expected to be mutually exclusive, as order of execution of the version couldn’t be determined.

NoMatchFoundCallback (optional)- called if request version doesn’t match the version provided in the options. If this callback is not provided latest version callback is called.

How version is determined for each request ?

Default behaviour is to use accept-version headers from the client.

This can be overridden by using a middleware and providing version in req.version property.

How versions are matched ?

semver versioning format is used to match version if versions are provided in semver format, supports ^,~ symbols on the server, else direct mapping is used (for versions like 1, 1.1)

Examples

Examples are available here

Test

npm test