Standardized API responses for NestJS

- Metadata-based wrapper to provide customizable and standardized API response objects;
- Built-in handling of pagination, sorting and filtering;
- Allows route handlers to keep returning classes instead of wrapper objects, so they remain fully compatible with interceptors;
- Automatic OpenAPI documentation with proper response schema for all features
- Generation of OpenAPI response examples with proper serialization for each user role

Getting started

🚀   Install

``shell
$ npm install nest-standard-response
`



🔮   Add to your app's `imports` array

`app.module.ts`

`ts
import { StandardResponseModule } from 'nest-standard-response';

@Module({
imports: [
StandardResponseModule.forRoot(options), // options can be ommited
],
controllers: [AppController],
providers: [AppService],
})
export class AppModule {}
`

Check out the options that this module accepts in the Advanced Configuration section.

📦   All routes are now wrapped

By default, all routes are automatically wrapped in a standard response object:

> To skip wrapping a particular route, just decorate the handler with @RawResponse().

> It's possible to invert this behavior to not wrap any route automatically, and only wrap routes annotated with @StandardResponse() instead. Check out how.

🚦   Wrapping only happens at the end of the NestJS' request pipeline

So interceptors like `ClassSerializer` and `RoleSerializer` work transparently without any custom logic.

🔥   Add features to your route

Just decorate a route with @StandardResponse({...options}) and pass in the options you want. Adding features will:

- Automatically prepare a route to receive query parameters for that feature;
- Parse and validate the input of these query parameters, and make them injectable into the handler;
- Add fields to the response object to let the client know the state of these features (and to allow discoverability of defaults when the route is called without any query params);
- Add documentation to Swagger with fully qualified schemas and examples;

To access this information during the request, use the @StandardParam() parameter decorator to inject a params object into your handler. This object contains the parsed query params, all the configuration values you set in the `@StandardResponse()`, plus methods to manipulate and add data into the response.

🎁   Combine features!

Features can be freely combined, or used all at once.

For example, using the features shown bellow, the route could be called like this:

>`/books?limit=8&offset=16&sort=-author,title&filter=author^=Frank;year>=1960;year>=1970`
> Note: This url was NOT url-encoded for readability (but you would need to encode yours)

For detailed information on the objects generated by filtering and sorting, as well as a list of all operations available, see the documentation for the @StandardParam() decorator.

---------------------------------------------------------------------------

Reference

A decorator that wraps the return of a route into a standardized API response object (while still allowing the handler to return true DTOs or other model class instances — this makes interceptors like caching, `ClassSerializer`, or `RoleSerializer` work transparently.)

The wrapper allows custom messages to be set in the response, and has optional features to handle common tasks, like pagination, sorting and filtering.

It can also optionally apply swagger's documentation, providing the correct combined schema for the DTO and the wrapper including any of its features. If given an array of Roles, it can also build Swagger route response examples for each user role, containing the reponse as it would be serialized for that user group.

` ts
import { UserDto } from './dto/user.dto';

@Controller('users')
export class UsersController {
constructor(
private readonly usersService: UsersService,
) {}

@Get('/')
@StandardResponse({ type: [UserDto] })
async findAll(): Promise {
const users = await this.usersService.findAll();
return users // <--- returns an array of UserDtos
}
}

// get /api/users
// Response:
{
"success": true,
"isArray": true,
"data": [
Users... // <--- The returned array is delivered inside the data property
]
}
`

(TODO image of swagger UI with the response examples dropdown open. Comparing a response for User and Admin, with arrows showcasing the extra fields returned only to admin)

🔸   StandardResponseOptions

---------------------------------------------------

🟠   @RawResponse()

The default behavior of StandardResponse is to wrap the response from all routes application wide. This keeps the API consistent and predictable. However, if you need to skip this behavior for a particular route, just set the `@RawResponse()` decorator:

`ts
@Controller('external-api-integration')
export class ExternalApiIntegrationController {
@Get('/')
@RawResponse() // <--- will skip wrapping
async findAll(): Promise {
return customObject;
}
}
`


If you're adding StandardResponse into an existing app, it might be useful to invert this behavior to create a gradual transition path. To do this, set the `interceptAll` option to `false` when importing the `StandardResponseModule` in your application. This way, routes will only be wrapped if they have explicitly set the `@StandardResponse()` decorator. See more information in the "Configuring" section bellow.

---------------------------------------------------

🟠   @StandardParam()

A parameter decorator used to inject a `StandardParams` object in the route handler.

This object allows access to:

* All options set in `@StandardResponse()`;
* Information captured from query parameters, parsed and validated;
* Methods to include and modify fields in the response object;

` ts
import { UserDto } from './dto/user.dto';

@Controller('users')
export class UsersController {
constructor(
private readonly usersService: UsersService,
) {}

@Get('/')
@StandardResponse({
type: [UserDto],
isPaginated: true,
maxLimit: 24,
defaultLimit 12,
})
async findAll(
@StandardParam() params: StandardParams // <--- inject into handler
): Promise {
const [users, count] = await this.usersService.findAll({
limit: params.pagination.limit,
offset: params.pagination.offset,
});
params.setPaginationInfo({ count: 348 }) // <--- set additional info
return users;
}
}

// get /api/users?limit=15&offset=30
// Response:
{
"success": true,
"isArray": true,
"isPaginated": true,
"pagination: {
count: 348, // <--- added inside the handler
limit: 15, // <--- from query
offset: 30,
maxLimit: 24, // <--- from decorator options
defaultLimit: 12,
}
"data": [
Users...
]
}
`

The params object injected with @StandardParam() contains these keys:

🔸   PaginationInfo

🔸   SortingInfo

🔸   FilteringInfo


These rules are similar to other APIs like Google Analytics or Matomo Analytics.


🔸   Building the search query

When building a query, all AND operations should be separated by a semicolon (;), and all OR operations should be separed by a comma (,). For example:

This query will filter all books available for lending, which were first published in France OR Italy, between 1970 AND 1999, whose author starts with Vittorio OR ends with Alatri:

`
available==true;country==France,country==Italy;year>=1970;year<=1999;author=^Vittorio,author=$Alatri
`

The resulting parsed object from this query will be:

`ts
{ allOf: [
{ anyOf: [
{ field: 'available', operation: '==', value: true },
]},
{ anyOf: [
{ field: 'country', operation: '==', value: 'France' },
{ field: 'country', operation: '==', value: 'Italy' },
]},
{ anyOf: [
{ field: 'year', operation: '>=', value: 1970 },
]},
{ anyOf: [
{ field: 'year', operation: '<=', value: 1999 },
]},
{ anyOf: [
{ field: 'author', operation: '=^', value: 'Vittorio' },
{ field: 'author', operation: '=$', value: 'Alatri' },
]},
]}
`



---------------------------------------------------

🟠   Advanced configuration

✅ validateResponse

Allows you to provide a validation function to stop the return of a route if certain conditions are met.

For example: this can abort a request if a route tries to return — instead a DTO — a raw DB document or some other object that may leak information not intended to be exposed.

This function should return `false` to abort the request.

`ts
@Module({
imports: [
StandardResponseModule.forRoot({
validateResponse: (data) => {
if (isMongooseObject(data)) return false;
return true;
},
}),
],
controllers: [AppController],
providers: [AppService],
})
export class AppModule {}
`

✅ interceptAll

Setting `interceptAll` to `false` will invert the default behavior of wrapping all routes by default, and will instead only wrap routes decorated with `@StandardResponse()`.

`ts
@Module({
imports: [
StandardResponseModule.forRoot({
interceptAll: false
}),
],
controllers: [AppController],
providers: [AppService],
})
export class AppModule {}
`

---------------------------------------------------

🚀   TODO Milestones

- Allow setting any custom field in the repsonse object by exposing a method in the StandardParam: `setExtra(field, value)``;

🏭 ⭐️ 🕹️ 💡 💎 🔩 ⚙️ 🧱 🔮 💈 🛍️ 🎁 🪭 ⚜️ ❇️ 🚩
📦 🏷️ 📮
🟠 🟧 🔶 🔸