Skip to content

minor spelling and grammar changes UPGRADE-v2.0.md #517

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
Aug 4, 2017
Merged

minor spelling and grammar changes UPGRADE-v2.0.md #517

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
14 changes: 7 additions & 7 deletions UPGRADE-v2.0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@
have been quite simplified, without the need to define a explicit Metaclass for each subtype.

It also improves the field resolvers, [simplifying the code](#simpler-resolvers) the
developer have to write to use them.
developer has to write to use them.

**Deprecations:**
* [`AbstractType`](#abstracttype-deprecated)
Expand All @@ -20,14 +20,14 @@ developer have to write to use them.
* [`Meta as Class arguments`](#meta-ass-class-arguments) (_only available for Python 3_)


> The type metaclases are now deleted as are no longer necessary, if your code was depending
> The type metaclasses are now deleted as they are no longer necessary. If your code was depending
> on this strategy for creating custom attrs, see an [example on how to do it in 2.0](https://github.com/graphql-python/graphene/blob/2.0/graphene/tests/issues/test_425.py).

## Deprecations

### Simpler resolvers

All the resolvers in graphene have been simplified. If before resolvers must had received
All the resolvers in graphene have been simplified. If before resolvers required
four arguments `root`, `args`, `context` and `info`, now the `args` are passed as keyword arguments
and `context` and `info` will only be passed if the function is annotated with it.

Expand Down Expand Up @@ -112,7 +112,7 @@ class User(ObjectType):

### Mutation.Input

`Mutation.Input` is now deprecated in favor using `Mutation.Arguments` (`ClientIDMutation` still uses `Input`).
`Mutation.Input` is now deprecated in favor of using `Mutation.Arguments` (`ClientIDMutation` still uses `Input`).

Before:

Expand All @@ -135,7 +135,7 @@ class User(Mutation):

### Simpler resolvers

All the resolvers in graphene have been simplified. If before resolvers must had received
All the resolvers in graphene have been simplified. If before resolvers required
four arguments `root`, `args`, `context` and `info`, now the `args` are passed as keyword arguments
and `context` and `info` will only be passed if the function is annotated with it.

Expand Down Expand Up @@ -212,7 +212,7 @@ class Query(ObjectType):

## Node.get_node

The method `get_node` in `ObjectTypes` that have `Node` as interface, changes it's api.
The method `get_node` in `ObjectTypes` that have `Node` as interface, changes its API.
From `def get_node(cls, id, context, info)` to `def get_node(cls, info, id)`.

```python
Expand Down Expand Up @@ -251,7 +251,7 @@ Now only receives (`root`, `info`, `**input`)
### InputObjectType

If you are using `InputObjectType`, you now can access
it's fields via `getattr` (`my_input.myattr`) when resolving, instead of
its fields via `getattr` (`my_input.myattr`) when resolving, instead of
the classic way `my_input['myattr']`.

And also use custom defined properties on your input class.
Expand Down