Skip to content

Commit c8d3546

Browse files
docs: make mongodb custom params section more clear
It's not clear to newcomers that custom params should not be exposed to the client. I've linked to the place where we mention this in the docs.
1 parent efb13de commit c8d3546

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/api/databases/mongodb.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -90,7 +90,7 @@ The `find` method has been split into separate utilities for converting params i
9090

9191
### Custom Params
9292

93-
The `@feathersjs/mongodb` adapter utilizes three custom params which control adapter-specific features: `params.pipeline`, `params.mongodb`, and `params.adapter`.
93+
The `@feathersjs/mongodb` adapter utilizes three custom params which control adapter-specific features: `params.pipeline`, `params.mongodb`, and `params.adapter`. As mentioned [here](/api/services#params), these custom params are not intended to be used directly from the client. Directly exposing `params.pipeline` or `params.mongodb` to the client directly would expose the entire database to the client through powerful pipeline queries.
9494

9595
#### params.adapter
9696

0 commit comments

Comments
 (0)