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.

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

[docs] Abstract Types - note about resolve_type #1247

Merged
merged 1 commit into from
Jan 29, 2018
Merged
Changes from all commits
Commits
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
4 changes: 2 additions & 2 deletions guides/types/abstract_types.md
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ end

## Type-Level Resolution Hooks

Instead of a single, top-level `resolve_type` function, you can provide type-level functions:
In addition to a single, top-level `resolve_type` function, you can provide type-level functions:

```ruby
MyUnion = GraphQL::UnionType.define do
Expand All @@ -52,7 +52,7 @@ MyInterface = GraphQL::InterfaceType.define do
end
```

These functions take priority over the schema-level function.
Keep the schema-level `resolve_type` function: these type-level functions take priority over the schema-level function.

## Orphan Types

Expand Down