Skip to content

graphql 3.0 and graphene 3.0 final rebase#951

Merged
jkimbo merged 13 commits into
v3from
unknown repository
May 9, 2020
Merged

graphql 3.0 and graphene 3.0 final rebase#951
jkimbo merged 13 commits into
v3from
unknown repository

Conversation

@ghost

@ghost ghost commented Apr 29, 2020

Copy link
Copy Markdown

I rebased almost all change to their original author: form #905 and #774.

@ghost ghost requested review from jkimbo and ulgens April 29, 2020 13:50
@ghost ghost changed the title WIP: @ulgens plus fixing ResolveInfo v3: @ulgens #905 plus fixing ResolveInfo Apr 29, 2020
@ghost ghost marked this pull request as ready for review April 29, 2020 13:58
@ghost ghost changed the title v3: @ulgens #905 plus fixing ResolveInfo v3: #905 plus fixing ResolveInfo Apr 29, 2020

@winged winged left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, apart from some minor issues.

Maybe also update the commit from @ulgens to contain all the notes from the squashed commits

Comment thread graphene_django/converter.py Outdated
Comment thread setup.py Outdated
@ghost

ghost commented May 1, 2020

Copy link
Copy Markdown
Author

@jkimbo I reviewed the PR with my college @winged.

  • I will fix setup.py

  • And move the relevant commit messages from all the v3-attempts into the main-commit

Then we think, it can be merged into v3. Then I try v3 with caluma.

@jkimbo jkimbo left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is looking good thanks @ganwell ! 1 minor suggestion.

Comment thread README.rst Outdated
@jkimbo

jkimbo commented May 1, 2020

Copy link
Copy Markdown
Member

@ganwell I've just merged the github actions migration into v3 so you'll have to rebase this change on top of that (sorry)

Jean-Louis Fuchs and others added 13 commits May 4, 2020 12:05
* Update mentions of django 1.11 and 2.0
Fields starting with __ are reserved for introspection
Connection resolvers have access to pagination arguments.
Some of the tests show the problem described here: graphql-python/graphql-core#61
It was only needed for Python 2.7
…ray_slice

connection_from_list_slice:
> Deprecated alias for connection_from_array_slice. We're now using the
JavaScript terminology in Python as well, since list is too narrow a
type and there is no other really appropriate type name.

https://github.com/graphql-python/graphql-relay-py/blob/v3.0.0/src/graphql_relay/connection/arrayconnection.py#L54
* names must be strings

* update to expected schemas to new format

* Call get() on django promises to get the actual value
@ghost ghost changed the title v3: #905 plus fixing ResolveInfo graphql 3.0 and graphene 3.0 final rebase May 4, 2020
@ghost

ghost commented May 4, 2020

Copy link
Copy Markdown
Author

@jkimbo this is hopfully the final rebase. I rebased all original commits from @ktosiek and @ulgens in to this PR. The diff to the version that was reviewed is trivial: https://git.io/Jfsh3

@winged winged left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like :) Nice work on the rebase / re-include of the contributors as well!

@jkimbo jkimbo left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍looks good @ganwell . Thanks for all your work on this!

@jkimbo jkimbo merged commit 10d22de into graphql-python:v3 May 9, 2020
This was referenced May 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants