-
Notifications
You must be signed in to change notification settings - Fork 228
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
Graphene v3 (tests) #317
Graphene v3 (tests) #317
Conversation
Fix #248 |
The same has been done in graphene.
Python 3 bundles mock in stdlib.
Allow for some flexibility on version numbers.
As we're targeting Python >= 3.6, this module should always be in stdlib.
SQLAlchemy 1.4+ does not export Binary directly. We should decide whether to keep this test, update for another unknown type, or remove it altogether.
ChoiceType no longer relies on EnumMeta but instead it exposes a ``type_impl`` field that we can leverage to decide whether the internal ``choices`` is a tuple of enum members or a tuple of tuples (pairs)
Thanks for the great work! Inspired by the existing work, I gave it a try to support sqlalchemy1.4 and passed all test cases https://github.com/richin13/graphene-sqlalchemy/pull/2. I constructed |
Support sqlalchemy1.4
Hey @mvanlonden 👋🏼 can you help us get this reviewed? |
Codecov Report
@@ Coverage Diff @@
## master #317 +/- ##
==========================================
- Coverage 97.65% 96.91% -0.74%
==========================================
Files 9 9
Lines 596 616 +20
==========================================
+ Hits 582 597 +15
- Misses 14 19 +5
Continue to review full report at Codecov.
|
@richin13 thanks for adding graphene v3 support. Is it possible to backport sqlalchemy 1.4 support to latest stable version 2.3? I'm using sqlalchemy 1.4 and really want to test the batching ability before graphene v3 is GA. Thanks! |
This PR builds on top of #306 and fixes all failing tests. It replaces the
promises.dataloader
withaiodataloader
making batched queries asyncio-dependant. The tests were update to account for this change.I had to pin sqlalchemy to<1.4
becauseQueryContext
changed its API in 1.4, happy to revisit this decision after pushing the v3 release to unblock graphene's road to v3Thanks to @colelin26 for adding support for SQLAlchemy 1.4; the above is no longer true.