middleware-body

HTTP request body parser middleware for Marble.js.
Installation
yarn add @marblejs/middleware-body
Requires @marblejs/core to be installed.
Importing
import { bodyParser$ } from '@marblejs/middleware-body';
Type declaration
bodyParser$ :: BodyParserOptions -> HttpMiddlewareEffect
Parameters
parameter
definition
options
<optional> BodyParserOptions
BodyParserOptions
parameter
definition
parser
<optional> RequestBodyParser
type
<optional> Array<string>
The type option is used to determine what media type the middleware will parse. It is passed directly to the type-is library and this can be an extension name (like json), a mime type (like application/json), or a mime type with a wildcard (like */* or */json). Defaults to */*.
Basic usage
app.ts
import { bodyParser$ } from '@marblejs/middleware-body';
​
export default httpListener({
  middlewares: [bodyParser$()],
  effects: [/* ... */],
});
Lets assume that we have the following CURL command, which triggers POST /api/login endpoint:
$ curl --header "Content-Type: application/json" \
  --request POST \
  --data '{ "username": "foo", "password": "bar" }' \
  http://localhost:3000/api/login
Using previously connected bodyParser$  middleware, the app will intercept the following payload object:
req.body = {
  username: 'foo',
  password: 'bar',
};
The POST request body can be intercepted like follows.
login.effect.ts
import { r } from '@marblejs/core';
​
export const login$ = r.pipe(
  r.matchPath('/login'),
  r.matchType('POST'),
  r.useEffect(req$ => req$.pipe(
    map(req => req.body as { username: string, password: string })
    map(body => ({ body: `Hello, ${body.username}!` }))
  )));
All properties and values in req.body object are untrusted (unknown) and should be validated before trusting.
This middleware does not handle multipart bodies.
Advanced usage
The middleware does nothing if request Content-Type is not matched, which makes a possibility for chaining multiple parsers one after another. For example, we can register multiple middlewares that will parse only a certain set of possible Content-Type headers. 
Default parser:
import { bodyParser$ } from '@marblejs/middleware-body';
​
bodyparser$();
Parses application/json (to JSON), application/x-www-form-urlencoded (to JSON), application/octet-stream (to Buffer) and text/plain (to string) content types
JSON parser:
import { bodyParser$, jsonParser } from '@marblejs/middleware-body';
​
bodyParser$({
  parser: jsonParser,
  type: ['*/json', 'application/vnd.api+json'],
})
Parses req.body to JSON object.
URLEncoded parser:
import { bodyParser$, urlEncodedParser } from '@marblejs/middleware-body';
​
bodyParser$({
  parser: urlEncodedParser,
  type: ['*/x-www-form-urlencoded'],
});
Parses encoded URLs req.body to JSON object.
Text parser:
import { bodyParser$, textParser } from '@marblejs/middleware-body';
​
bodyParser$({
  parser: textParser,
  type: ['text/*'],
});
Parses req.body to string.
Raw parser:
import { bodyParser$, rawParser } from '@marblejs/middleware-body';
​
bodyParser$({
  parser: rawParser,
  type: ['application/octet-stream'],
}),
Parses req.body to Buffer.
Custom parsers
If the available parsers are not enough, you can create your own body parsers by conforming to RequestBodyParser interface. The example below shows how the jsonParser looks underneath.
export const jsonParser: RequestBodyParser = req => body =>
  JSON.parse(body.toString());
middleware-logger
Next - Other
Style Guide
Last updated 11 months ago
parameter	definition
parser	<optional> `RequestBodyParser`
type	<optional> `Array<string>`