Skip to content

Commit 56f1064

Browse files
committed
changed readme
1 parent 59ffb11 commit 56f1064

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -15,12 +15,12 @@ The main differences to the @js-entity-repos/express:
1515

1616
- different naming convention: using `item` instead of `entity`
1717
- cursor based pagination operates using `before` and `after` instead of `cursor` and `direction`
18-
- `enveloping` response (GET /items) which allows client to more easily discover the pagination and metadata
18+
- optional `enveloping` response (`GET /endpoint?envelope=true`) for clients not capable of working with headers and JSONP
1919
- `granular transactions handlers` for each `request handler` - this could be used for i.e. `authentication` or `permissions` checks
2020
- possibility to `override` each `request handler`
2121
- ability to disable json body parser middleware if already present in the stack (`enableJsonBodyParser: false`)
22-
- by default all responses are `pretty` which improves readability, you can disabled that by query param (`/endpoint?pretty=false`)
23-
- dropped support for `/count` endpoint, instead allows client to get number of available items by adding query param (`/endpoint?total=true` for get request, resulting in additional header: `x-total-count`)
22+
- by default all responses are `pretty` which improves readability, you can disabled that by query param (`/endpoint?pretty=false`)
23+
- dropped support for `/count` endpoint, instead allows client to get number of available items by adding query param (`/endpoint?total=true` for get request, resulting in additional header: `x-total-count`)
2424

2525
## Installation:
2626

0 commit comments

Comments
 (0)