Skip to content

Commit

Permalink
Merge pull request #994 from Moe-Hassan-123/patch-1
Browse files Browse the repository at this point in the history
fix typo in guides/input/filtering
  • Loading branch information
vitalik authored Dec 10, 2023
2 parents cb16748 + 4a81ee1 commit c548ea5
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/docs/guides/input/filtering.md
Original file line number Diff line number Diff line change
Expand Up @@ -62,7 +62,7 @@ By default, the filters will behave the following way:
* `None` values will be ignored and not filtered against;
* Every non-`None` field will be converted into a `Q`-expression based on the `Field` definition of each field;
* All `Q`-expressions will be merged into one using `AND` logical operator;
* The resulting `Q`-expression is used to filter the queryset and return you a qeryset with a `.filter` clause applied.
* The resulting `Q`-expression is used to filter the queryset and return you a queryset with a `.filter` clause applied.

## Customizing Fields
By default, `FilterSet` will use the field names to generate Q expressions:
Expand Down Expand Up @@ -182,4 +182,4 @@ class BookFilterSchema(FilterSchema):
)
return q
```
The `custom_expression` method takes precedence over any other definitions described earlier, including `filter_<fieldname>` methods.
The `custom_expression` method takes precedence over any other definitions described earlier, including `filter_<fieldname>` methods.

0 comments on commit c548ea5

Please sign in to comment.