Skip to content

rename ExecutionTypeInfo #4

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

Merged
merged 1 commit into from
Oct 17, 2018
Merged

rename ExecutionTypeInfo #4

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
8 changes: 4 additions & 4 deletions content/documentation/master/data-fetching.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -177,7 +177,7 @@ system designer is how you will use context in your fetchers if at all. Some pe
data fetchers automatically and hence don't need to use this.


* ``ExecutionTypeInfo getFieldTypeInfo()`` - the field type information is a catch all bucket of field type information that is built up as
* ``ExecutionStepInfo getExecutionStepInfo()`` - the field type information is a catch all bucket of field type information that is built up as
the query is executed. The following section explains more on this.

* ``DataFetchingFieldSelectionSet getSelectionSet()`` - the selection set represents the child fields that have been "selected" under neath the
Expand All @@ -189,12 +189,12 @@ query.



## The interesting parts of ExecutionTypeInfo
## The interesting parts of ExecutionStepInfo

The execution of a graphql query creates a call tree of fields and their types. ``graphql.execution.ExecutionTypeInfo.getParentTypeInfo``
The execution of a graphql query creates a call tree of fields and their types. ``graphql.execution.ExecutionStepInfo.getParentTypeInfo``
allows you to navigate upwards and see what types and fields led to the current field execution.

Since this forms a tree path during execution, the ``graphql.execution.ExecutionTypeInfo.getPath`` method returns the representation of that
Since this forms a tree path during execution, the ``graphql.execution.ExecutionStepInfo.getPath`` method returns the representation of that
path. This can be useful for logging and debugging queries.

There are also helper methods there to help you get the underlying type name of non null and list wrapped types.
Expand Down