-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
3 changed files
with
23 additions
and
0 deletions.
There are no files selected for viewing
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
Resolvers | ||
========= | ||
|
||
Resolvers define how to fetch the data defined in your schema. There are many | ||
ways to access your data but resolvers are just a simple async function that | ||
return either an object or a dictionary that matches the shape of the Schema | ||
return type. | ||
|
||
This could be the raw json response from a third party library or it could be | ||
a database model that represents your data. The great thing about resolvers | ||
are they are completely flexible as long as the type you are returning is correct. | ||
Which means you can combine loosly related items into a single parent. | ||
|
||
.. toctree:: | ||
:maxdepth: 2 | ||
|
||
.. automodule:: cannula.api | ||
:members: |