Releases: graphql-python/graphql-server
Releases · graphql-python/graphql-server
v3.0.0b7
Sorry, something went wrong.
No results found
What's Changed
Full Changelog: v3.0.0b6...v3.0.0b7
v3.0.0b6
Sorry, something went wrong.
No results found
What's Changed
New Contributors
Full Changelog: v3.0.0b5...v3.0.0b6
v3.0.0b5
Sorry, something went wrong.
No results found
Cito
released this
26 May 14:03
- Empty fields are not contained in formatted errors any more
- Accept Graphene wrapped GraphQL schemas
- Update GraphQL-core from 3.1 to 3.2 (#85)
v3.0.0b4
Sorry, something went wrong.
No results found
jkimbo
released this
10 Aug 12:14
- Add support for validation rules (#83)
v3.0.0b2
Sorry, something went wrong.
No results found
This is the second beta version of graphql-server
This version only introduces a small fix for async mode when graphiql option is enabled for aiohttp and sanic (#67).
Also updates the GH CI to submit the coverage to codecov.
v3.0.0b1
Sorry, something went wrong.
No results found
This is the first beta version of graphql-server.
This is based on GraphQL-core 3 and supports Python 3.6+ along with other nice features from graphql.
The main changes on this version are:
- Now supports all graphql-core 3 features and removes unsupported ones (#36):
- No longer supports executor features (was only at graphql-core 2). (#40)
- All server integrations (Flask, Webob, Sanic, aiohttp) are merged into this package to provide a better development workflow by providing the same changes to all of them. (#37 #38 #42 #45)
- Now all server integration docs are available at this repo. (#54)
- Update graphiql to 1.0.3 and brings some latest features like passing and persisting headers, subscriptions, etc. (#49 #55)
- Improve the parsing and validation steps and also allows passing custom validation rules and limit the number of reported errors. (#53)
v2.0.0
Sorry, something went wrong.
No results found
jkimbo
released this
17 Mar 17:34
This release doesn't contain any breaking changes, it's just bringing everything up to date in preparation for a v3 release.
Thanks to @KingDarBoja for all the hard work on bringing this library up to date!