You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+14-14Lines changed: 14 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,9 @@
1
-
Please read [UPGRADE-v2.0.md](/UPGRADE-v2.0.md) to learn how to upgrade to Graphene `2.0`.
1
+
**We are looking for contributors**! Please check the [ROADMAP](https://github.com/graphql-python/graphene/blob/master/ROADMAP.md) to see how you can help β€οΈ
Also, Graphene is fully compatible with the GraphQL spec, working seamlessly with all GraphQL clients, such as [Relay](https://github.com/facebook/relay), [Apollo](https://github.com/apollographql/apollo-client) and [gql](https://github.com/graphql-python/gql).
29
27
@@ -39,7 +37,6 @@ pip install "graphene>=2.0"
39
37
40
38
Please read [UPGRADE-v2.0.md](/UPGRADE-v2.0.md) to learn how to upgrade.
41
39
42
-
43
40
## Examples
44
41
45
42
Here is one example for you to get started:
@@ -67,9 +64,8 @@ result = schema.execute(query)
67
64
68
65
If you want to learn even more, you can also check the following [examples](examples/):
Graphene supports several versions of Python. To make sure that changes do not break compatibility with any of those versions, we use `tox` to create virtualenvs for each python version and run tests with that version. To run against all python versions defined in the `tox.ini` config file, just run:
98
+
102
99
```sh
103
100
tox
104
101
```
102
+
105
103
If you wish to run against a specific version defined in the `tox.ini` file:
104
+
106
105
```sh
107
106
tox -e py36
108
107
```
108
+
109
109
Tox can only use whatever versions of python are installed on your system. When you create a pull request, Travis will also be running the same tests and report the results, so there is no need for potential contributors to try to install every single version of python on their own system ahead of time. We appreciate opening issues and pull requests to make graphene even more stable & useful!
In order to move Graphene and the GraphQL Python ecosystem forward I realized is essential to be clear with the community on next steps, so we can move uniformly.
4
+
5
+
There are few key points that need to happen in the short/mid term, divided into two main sections:
6
+
7
+
-[Community](#community)
8
+
-[Graphene 3](#graphene-3)
9
+
10
+
_π If you have more ideas on how to move the Graphene ecosystem forward, don't hesistate to [open a PR](https://github.com/graphql-python/graphene/edit/master/ROADMAP.md)_
11
+
12
+
## Community
13
+
14
+
The goal is to improve adoption and sustainability of the project.
15
+
16
+
- π Add Commercial Support for Graphene #813
17
+
- Create Patreon page
18
+
- Add /support page in Graphene website
19
+
- π Vastly improve documentation #823
20
+
- π° Apply for [Mozilla MOSS](https://www.mozilla.org/en-US/moss/) sponsorship
21
+
22
+
## Graphene 3
23
+
24
+
The goal is to summarize the different improvements that Graphene will need to accomplish for version 3.
25
+
26
+
In a nushell, Graphene 3 should take the Python 3 integration one step forward while still maintaining compatibility with Python 2.
27
+
28
+
- π [graphql-core-next](https://github.com/graphql-python/graphql-core-next) GraphQL engine support (almost same API as graphql-core)
29
+
- πΈ GraphQL types from type annotations #729
30
+
- π Schema creation from SDL (API TBD)
31
+
- β¨ Improve connections structure
32
+
- π Improve function documentation
33
+
- π Add support for coroutines in Connection, Mutation (abstracting out Promise requirement)
0 commit comments