post-controller-router

Controller router dedicated for update requests

Extension to controler-router which splits controller into validation and submission steps, and provides option to pass processing to remote entity.

It can be used to e.g. handle form submissions in browsers, or POST requests on server-side, but on its own doesn't provide any, ready to use, bindings to handle such requests. They need to be configured on top, externally.

For full picture be sure to read controler-router documentation first.

Basic usage example:

var PostControllerRouter = require('post-controller-router');
 
var postRouter = new PostControllerRouter({
  register: {
        validate: function (data) {
            if (!data.email) {
                throw new TypeError("Email value missing");
            }
            if (data.email.indexOf('@') === -1) {
                throw new TypeError("Invalid email");
            }
            if (!data.passport) {
                throw new TypeError("Password value missing");
            }
            return data;
        },
        submit: function (data) {
            registerAccount(data.email, data.password);
        }
    }
});
 
postRouter.route('/register/', {}); // Throws: "Email value missing"
postRouter.route('/register/', { email: '[e-mail]', password: 'abc123' }); // Ok

Installation

$ npm install post-controller-router

API

PostControllerRouter constructor properties

PostControllerRouter.ensureRoutes(routes[, options])

Validates provided routes configuration with respect to provided options. It's also used internally on router initialization.

Options are explained at router initialization section.

PostControllerRouter.resolveRoutes(routes[, options])

Resolves complete post controller routes map with respect to provided options, e.g. it fills not provided submit functions with default submit as provided in options.
Input routes object is left intact, new one is returned. It is assumed that input routes are valid (as assured by ensureRoutes function). This function is also used internally at router initialization.

Options are explained at router initialization section.

PostControllerRouter.normalizeRoutes(routes[, options])

Normalizes routes map up into basic ControllerRouter format. So e.g. submit and validate are merged into one controller function.
Input object is left intact, new one is returned. It is assumed that input routes are valid (as assured by ensureRoutes function). This function is used internally at router initialization.

Options are explained at router initialization section.

PostControllerRouter initialization

new PostControllerRouter(routes[, options])

var PostControllerRouter = require('post-controller-router');
 
var postRouter = new PostControllerRouter({
  // Routes configuration
}, {
    // Options
});
 
router.route('/foo/bar', data); // invoke controller for '/foo/bar' path with given data

PostControllerRouter on initialization accepts routes map configuration and returns, and eventual options

Initialization options

All of the options are optional

• validate: Default validation function. For routes where validate function was not provided, this function would be used instead.
• submit: Default submit function. For routes where submit function was not provided, this function would be used instead.
• remoteSubmit: Default remote submission logic. For routes where remoteSubmit was configured as remoteSubmit: true, this function will be used invoke remote submission.

For more details on validate, submit and remoteSubmit flow, see Routes map: controller values section.

Routes map configuration

Routes map is a configuration of key value, pairs, where key is a path, and value is a controller configuration.

Routes map: path keys

Please refer to controller-router documentation.

Routes map: controller values

Typical controller would be configured out of validate and submit functions, which on router call will be invoked one after another.

• validate(...args) Validates request for given path. Its run in event context as described in controller-router documentation, and receives all arguments which were passed to route (or routeEvent) methods.
  If validation fails, validate function should throw to prevent submission step.
  validate may return a promise object, in such case invocation of submit would be postponed until promise resolves
• submit(validateResult, ...args) Submits given request. Its run in event context as described in controller-router documentation, receives resolved result of validate function, and all arguments which were passed to route (or routeEvent) methods.

In some cases, we may want to pass submission for remote processing. In such scenario we should provide validate and remoteSubmit (instead of submit) functions, and optionally we may provide a processResponse function which will be run to process response from remote server.

• remoteSubmit(validateResult, ...args) Submits given request to remote server. Its run in event context as described in controller-router documentation, receives resolved result of validate function, and all arguments which were passed to route (or routeEvent) methods.
  remoteSubmit naturally should return promise result
• processResponse(remoteSubmitResult) Processes resolved value as returned by remoteSubmit. Its run in event context as described in controller-router documentation.

Additionally for dynamic paths match function should be provided, refer to controller-router documentation for details.

If route path is static, and we want to rely strictly on default validate and submit functions (provided with intialization options), then we may configure route with plain true value, as in below example:

var postRouter = getPostRouter({
  foo: true,
  bar: true
}, {
  validate: defaultValidate,
  submit: defaultSubmit
});

PostControllerRouter instance properties

Follow controller-router documentation.

Tests

$ npm test