FastapiRequestStrategy
Request strategy for the FastAPI driver
Generates URIs for a FastAPI endpoint that filters with
fastapi-filter (its
SQLAlchemy backend) and paginates with
fastapi-pagination’s
Page:
- Filters:
field=value; several values become one comma-separatedfield__in=a,b, the only list form fastapi-filter reads (a repeated param keeps its last value) - Operator filters:
field__<operator>=value, translated fromFilterOperatorEnum—NOT→__neq/__not_in,CONTAINS→__like,ILIKE→__ilike,SW→__likeanchored at the start,BTW→__gte+__lte,NULL→__isnull=true|false - Ordering:
order_by=-field1,field2(-prefix = DESC) - Search:
search=term, an OR ofilikeacross the backend’ssearch_model_fields - Pagination:
page+size, the defaults of fastapi-pagination’sPage
fastapi-filter expects the client to send like/ilike wildcards, so
CONTAINS and ILIKE wrap the value in %…% and SW appends one %,
sent percent-encoded as %25. A % or _ inside the value itself is a
wildcard too: fastapi-filter has no escape.
order_by and size are the libraries’ own names and are fixed here,
the way DRF’s ordering and page_size are; page and search follow
QueryBuilderOptions.
Constructor
Section titled “Constructor”new FastapiRequestStrategy()Properties
Section titled “Properties”| Property | Type | Description |
|---|---|---|
capabilities |
StrategyCapabilities |
Filters, operator filters, sorts and global search — no select, fields, includes or embedded resources, none of which fastapi-filter has |
Methods
Section titled “Methods”assertResource()
Section titled “assertResource()”assertResource(state: QueryBuilderState): voidThrow if the resource is not set on the state
Centralises the message that was previously copy-pasted across four of the five concrete strategies.
| Parameter | Type | Description |
|---|---|---|
state |
QueryBuilderState |
The current query builder state |
baseUri()
Section titled “baseUri()”baseUri(state: QueryBuilderState): stringCompute the base path (no query string)
Exactly one slash joins the two: trailing slashes on the base URL and
leading slashes on the resource are dropped, so /projects/42/tasks
never becomes the protocol-relative //projects/42/tasks. A trailing
slash on the resource is kept, for backends whose routes end in one.
Nothing is encoded.
| Parameter | Type | Description |
|---|---|---|
state |
QueryBuilderState |
The current query builder state |
Returns — The base URI without the query separator (e.g. /users or https://api.example.com/users)
buildUri()
Section titled “buildUri()”buildUri(state: QueryBuilderState, options: QueryBuilderOptions): stringCompose the full request URI from the given state
Template method: validates the resource, computes the base path,
delegates the per-driver query-string segments to parts(...), and
joins them with the conventional ?/& separators.
parts(...) receives the state with filter values, operator-filter
values and the search term already percent-encoded (see
encodeValues), so no concrete strategy encodes on its own and none
can forget to.
| Parameter | Type | Description |
|---|---|---|
state |
QueryBuilderState |
The current query builder state |
options |
QueryBuilderOptions |
The query parameter key name configuration |
Returns — The composed URI string
join()
Section titled “join()”join(base: string, segments: string[]): stringGlue the base URI and the per-driver query-string segments
Returns the bare base when no segments were emitted (e.g. PostgREST
in RANGE mode with no filters), otherwise joins with ? + &.
| Parameter | Type | Description |
|---|---|---|
base |
string |
The base URI from _baseUri |
segments |
string[] |
The query-string fragments from parts(...) |
Returns — The full URI
parts()
Section titled “parts()”parts(state: QueryBuilderState, options: QueryBuilderOptions): string[]Emit FastAPI-format query-string segments in canonical order: filters → operator filters → order_by → search → page → size
| Parameter | Type | Description |
|---|---|---|
state |
QueryBuilderState |
The current query builder state |
options |
QueryBuilderOptions |
The query parameter key name configuration; page and search are read, while order_by and size are fixed |
Returns — Ordered query-string fragments
validateLimit()
Section titled “validateLimit()”validateLimit(limit: number): voidValidate that a limit value is acceptable for this driver
Default policy: positive integer. Drivers that recognise a sentinel
(NestJS treats -1 as “fetch all”) override this method.
| Parameter | Type | Description |
|---|---|---|
limit |
number |
The limit value to validate |
