-
Notifications
You must be signed in to change notification settings - Fork 3
2. Usage Examples
You can use the default middleware settings or customize them according to the needs of your application.
The middleware uses the following defaults:
options = {
default: {
pagination: {
limit: Number.MAX_SAFE_INTEGER,
skip: 0,
page: 1
},
fields: {},
sort: {},
filters: {}
},
use_page: false,
client_db: 'mongodb',
date_fields: {
'start_at': 'created_at',
'end_at': 'created_at'
}
}
These settings can be customized by the user, as long as they follow the standard defined in the middleware. Below we have the description of each of the parameters, as well as the definition of their default values.
Paging works in conjunction with two query strings: limit, skip/page.
-
limit
Determines the maximum number of items that the query should return,limit=30
returns a maximum of 30 items.- Default value:
limit: MAX_SAFE_INTEGER
(constant value for 9007199254740991)
- Default value:
Pagination with skip
-
skip
Determines the number of items you want to skip in the query, skip=20 ignore the first 20 items.- Default value:
skip: 0
- Default value:
Pagination with page
-
page
Determines the page number to return with the requested resource. The number of available pages is dynamic according to the number of records on the server and the limit per page set.- Default value:
page: 1
- Default value:
Allows you to retrieve only the information you want. To do this, simply provide the attribute/property names separated by commas. By default, there is no field selection defined.
Allows to apply sorting rules. To do this, simply provide the attribute/property names that will be used to sort the query result separated by comma. By default, there is no pre-defined sort parameter.
It consists of limiting the number of resources requested by specify some attributes and their expected values. It's possible to filter a collection by multiple attributes at the same time and allow to filter multiple values for an attribute. By default, there is no pre-defined filter parameter.
Defines whether query pagination will be done using page
if the value is true, or skip
if this value is false. By default, this parameter is set to false.
Defines which database is being used. Based on this parameter, the queries are treated in different ways. By default, this parameter is set to 'mongodb'.
Defines the name of the parameter that will be used in Date filters.
start_at: Defines the name of the parameter set with start date of the filter. By default, this parameter is set to 'created_at'.
end_at: Defines the name of the parameter set with end date of the filter. By default, this parameter is set to 'created_at'.
To use the default settings, just do as described in the example below:
const express = require('express')
const qs = require('query-strings-parser')
const app = express()
app.use(qs()) // middleware query-strings-parser
app.listen(3000, (req, res) => {
console.log('app listening on port 3000')
})
app.get('/', (req, res) => {
res.send('the query is:' + JSON.stringify(req.query))
})
When a query with query strings is performed, the request query parameter is updated, and transformed into a JSON object containing the following information:
/**
* Request: http://localhost:3000?fields=name,age&skip=10&limit=10&sort=created_at
* Result (req.query):
* {
* fields: { name: 1, age: 1 },
* sort: { created_at: 'asc' }
* filters: {},
* pagination: {
* skip: 10,
* limit: 10
* }
* }
*/
const express = require('express')
const qs = require('query-strings-parser')
const app = express()
app.use(qs({
use_page: true,
client_db: 'mongodb',
date_field: 'created_at'
default: {
fields: {_id: 0},
sort: { created_at: 'desc' },
filters: {},
pagination: {
page: 1,
limit: 100
}
}
}))
/**
* Request: http://localhost:3000?fields=name,age&age=30
* Result (req.query):
* {
* fields: {_id: 0, name: 1, age: 1},
* sort: { created_at: 'desc' }
* filters: {age: 30},
* pagination: {
* limit: 100,
* page: 1
* }
* }
*/
Note: The custom queries settings must follow the standard defined in the middleware to ensure the correct operation of queries.