Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed Typo in Filter Docs #5097

Merged
merged 1 commit into from
May 25, 2022
Merged

Fixed Typo in Filter Docs #5097

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion website/src/docs/hotchocolate/api-reference/extending-filtering.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@ With this in mind, we can have a deeper dive into filtering. Buckle up, this mig
At the core of the configuration API of filtering there sits a convention. The convention holds the whole
configuration that filtering needs to create filter types and to translate them to the database.
During schema creation, the schema builder asks the convention how the schema should look like.
The convention defines the names and descriptions of types and fields and also what the type should be used for properties
The convention defines the names and descriptions of types and fields and also what the type should be used for properties.
The convention also defines what provider should be used to translate a GraphQL query to a database query.
The provider is the only thing that is used after the schema is built.
Every field or operation in a filter type has a handler annotated.
Expand Down