larvitbase-api

REST http API base framework based on larvitbase

Installation

npm i larvitbase-api

Basic usage

In the file index.js:

const	Api	= require('larvitbase-api');

let	api;

api = new Api({
	'baseOptions':	{'httpOptions': 8001},	// sent to larvitbase
	'routerOptions':	{},	// sent to larvitrouter
	'reqParserOptions':	{},	// sent to larvitReqParser
});

api.start(function (err) {}); // callback

// Exposed stuff
//api.base	- larvitbase instance
//api.options	- the options sent in when instanciated
//api.apiVersions	- resolved versions of the API (subfolders to controllers folder)

//api.stop() // close httpServer

Then just start the file from shell:

node index.js

This will provide the following:

Show the README.md on /

Will print your apps README.md when the browser targets http://localhost:8001/

Run controllers

Will run controllers in your apps "controllers/X.X"-folder (or node_module/xxx/controllers/X.X, see larvitfs for details on the virtual filesystem the routing module uses for this). For example /foo will run the controller controllers/1.2/foo.js, given that 1.2 is the latest version. For details about how to write controllers, see larvitbase.

It is also possible to request a specific version fo the API. Consider:

• /foo -> controllers/1.2/foo.js
• /1.2/foo -> controllers/1.2/foo.js
• /1.0/foo -> controllers/1.0/foo.js

More detailed examples on controllers in node modules

• /foo -> (does not exist controllers/foo.js or controllers/X.X/foo.js) -> node_modules/some_module/controllers/X.X/foo.js (where X.X is the highest version number) or
• /foo -> (does not exist controllers/foo.js or controllers/X.X/foo.js) -> node_modules/some_module/controllers/foo.js

If any controller exists, in any version in the local app, that controller will have priority over all node modules. If a specific version is requested, that version is all that will be searched for in modules. To find a controller in a module of a specific version this version must be present in the local app, even if the directory is empty.

For example, when folder structure that looks like this:

app
|__ controllers
|__ node_modules
	|__ dependency
		|__ controllers
			|__ v1.0
				|__ bar.js

Requests for /bar and /v1.0/bar will return a 404. However, if we create a v1.0 directory in our apps controllers directory (see below), bar.js will be successfully resolved.

app
|__ controllers
|	|__ v1.0
|__ node_modules
	|__ dependency
		|__ controllers
			|__ v1.0
				|__ bar.js

Likewise, if any version of the api exists in the local app, unversioned controllers in modules will not be resolved.

Valid versions

We are using semver where we do the following:

1. Run .clean() to change for example "v2.1" to "2.1"
2. Add a patch version, so "2.1" becomes "2.1.0" (this is because patches should never change the API, just fix bugs and issues without changing spec)
3. Check the result with .valid()

Output raw JSON

Will write everything stored in res.data as JSON directly to the browser as application/json (except for the README.md, that is sent as text/markdown).