Skip to content
This repository was archived by the owner on Sep 6, 2022. It is now read-only.

Adapt code to Graphene 2.0 #30

Merged
merged 8 commits into from
Aug 27, 2017
Merged

Adapt code to Graphene 2.0 #30

merged 8 commits into from
Aug 27, 2017

Conversation

syrusakbary
Copy link
Member

Adapt code to Graphene 2.0

Related PR: graphql-python/graphene#500

@coveralls
Copy link

Coverage Status

Coverage increased (+0.06%) to 91.706% when pulling c869f7f on 2.0 into 70479ee on master.

@syrusakbary syrusakbary requested a review from ekampf July 27, 2017 05:21
@syrusakbary
Copy link
Member Author

@ekampf I've updated the code and refactored the registry code to make it easier to understand and more testable (in a similar way that graphene-django and graphene-sqlalchemy work).

Please review and let me know if you have any suggestion before merging!

@coveralls
Copy link

Coverage Status

Coverage increased (+0.06%) to 91.706% when pulling 8e4158b on 2.0 into 70479ee on master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.06%) to 91.706% when pulling fc520cf on 2.0 into 70479ee on master.

@ekampf
Copy link
Collaborator

ekampf commented Jul 27, 2017

@syrusakbary thanks! I will go over this over the weekend...

@coveralls
Copy link

Coverage Status

Coverage increased (+0.06%) to 91.706% when pulling f9f21d4 on 2.0 into 70479ee on master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.06%) to 91.706% when pulling e877bc9 on 2.0 into 70479ee on master.

@syrusakbary
Copy link
Member Author

Graphene 2.0 is now merged into master.
As I want to give some people to adapt before releasing the stable version I will merge this PR.

@ekampf please let me know if you have any suggestions by creating a PR (If you want me to take a look) or by pushing directly into master in this repo :)

@syrusakbary syrusakbary merged commit bd12301 into master Aug 27, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants