diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2021-09-08 00:10:59 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2021-09-08 00:10:59 +0300 |
| commit | f59e4c38bdd4145900f02f7268997c6c61458a32 (patch) | |
| tree | 8ebe3c6bbbc68f1cf5d3490543b61e062d8e2ec5 /doc/development/api_graphql_styleguide.md | |
| parent | 7b61371e55a79bffecceb80221a8a41e34fb9559 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/api_graphql_styleguide.md')
| -rw-r--r-- | doc/development/api_graphql_styleguide.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/api_graphql_styleguide.md b/doc/development/api_graphql_styleguide.md index 3c8d07610f0..8f781e9ff18 100644 --- a/doc/development/api_graphql_styleguide.md +++ b/doc/development/api_graphql_styleguide.md @@ -941,7 +941,7 @@ end ``` While you can use the same resolver class in two different places, -such as in two different fields where the same object is exposed, +such as in two different fields where the same object is exposed, you should never re-use resolver objects directly. Resolvers have a complex life-cycle, with authorization, readiness and resolution orchestrated by the framework, and at each stage [lazy values](#laziness) can be returned to take advantage of batching |