Initial v3 version

This version is not yet fully working (one small test to go).
This is mostly based on the hard work

Author: syrusakbary

.github/workflows/deploy.yml

@@ -6,6 +6,8 @@
 # Covers JetBrains IDEs: IntelliJ, RubyMine, PhpStorm, AppCode, PyCharm, CLion, Android Studio and WebStorm
 # Reference: https://intellij-support.jetbrains.com/hc/en-us/articles/206544839
 
+.DS_Store
+
 # User-specific stuff
 .idea/**/workspace.xml
 .idea/**/tasks.xml

.github/workflows/lint.yml

@@ -1,89 +1,159 @@
-# Contributing
+# Contributing to `graphql-server`
 
-Thanks for helping to make graphql-server awesome!
+First off, thanks for taking the time to contribute!
 
-We welcome all kinds of contributions:
+The following is a set of guidelines for contributing to `graphql-server` on GitHub.
+These are mostly guidelines, not rules. Use your best judgment, and feel free
+to propose changes to this document in a pull request.
 
-- Bug fixes
-- Documentation improvements
-- New features
-- Refactoring & tidying
+#### Table of contents
 
+[How to contribute](#how-to-contribute)
 
-## Getting started
+- [Reporting bugs](#reporting-bugs)
+- [Suggesting enhancements](#suggesting-enhancements)
+- [Contributing to code](#contributing-to-code)
 
-If you have a specific contribution in mind, be sure to check the [issues](https://github.com/graphql-python/graphql-server/issues) and [pull requests](https://github.com/graphql-python/graphql-server/pulls) in progress - someone could already be working on something similar and you can help out.
+## How to contribute
 
+### Reporting bugs
 
-## Project setup
+This section guides you through submitting a bug report for `graphql-server`.
+Following these guidelines helps maintainers and the community understand your report, reproduce the behavior, and find related reports.
 
-### Development with virtualenv (recommended)
+Before creating bug reports, please check
+[this list](#before-submitting-a-bug-report) to be sure that you need to create
+one. When you are creating a bug report, please include as many details as
+possible. Make sure you include the Python and `graphql-server` versions.
 
-After cloning this repo, create a virtualenv:
+> **Note:** If you find a **Closed** issue that seems like it is the same thing
+> that you're experiencing, open a new issue and include a link to the original
+> issue in the body of your new one.
 
-```console
-virtualenv graphql-server-dev
-```
+#### Before submitting a bug report
 
-Activate the virtualenv and install dependencies by running:
+- Check that your issue does not already exist in the issue tracker on GitHub.
 
-```console
-python pip install -e ".[test]"
-```
+#### How do I submit a bug report?
 
-If you are using Linux or MacOS, you can make use of Makefile command `make dev-setup`, which is a shortcut for the above python command.
+Bugs are tracked on the issue tracker on GitHub where you can create a new one.
 
-### Development on Conda
+Explain the problem and include additional details to help maintainers reproduce
+the problem:
 
-You must create a new env (e.g. `graphql-sc-dev`) with the following command:
+- **Use a clear and descriptive title** for the issue to identify the problem.
+- **Describe the exact steps which reproduce the problem** in as many details as
+  possible.
+- **Provide specific examples to demonstrate the steps to reproduce the issue**.
+  Include links to files or GitHub projects, or copy-paste-able snippets, which you use in those examples.
+- **Describe the behavior you observed after following the steps** and point out
+  what exactly is the problem with that behavior.
+- **Explain which behavior you expected to see instead and why.**
 
-```sh
-conda create -n graphql-sc-dev python=3.8
-```
+Provide more context by answering these questions:
 
-Then activate the environment with `conda activate graphql-sc-dev`.
+- **Did the problem start happening recently** (e.g. after updating to a new version of `graphql-server`) or was this always a problem?
+- If the problem started happening recently, **can you reproduce the problem in
+  an older version of `graphql-server`?** What's the most recent version in which the problem doesn't happen?
+- **Can you reliably reproduce the issue?** If not, provide details about how
+  often the problem happens and under which conditions it normally happens.
 
-Proceed to install all dependencies by running:
+Include details about your configuration and environment:
 
-```console
-pip install -e ".[dev]"
-```
+- **Which version of `graphql-server` are you using?**
+- **Which Python version `graphql-server` has been installed for?**
+- **What's the name and version of the OS you're using?**
 
-And you ready to start development!
+### Suggesting enhancements
 
-## Running tests
+This section guides you through submitting an enhancement suggestion for
+`graphql-server`, including completely new features and minor improvements to existing
+functionality. Following these guidelines helps maintainers and the community
+understand your suggestion and find related suggestions.
 
-After developing, the full test suite can be evaluated by running:
+Before creating enhancement suggestions, please check
+[this list](#before-submitting-an-enhancement-suggestion) as you might find out
+that you don't need to create one. When you are creating an enhancement
+suggestion, please
+[include as many details as possible](#how-do-i-submit-an-enhancement-suggestion).
 
-```sh
-pytest tests --cov=graphql-server -vv
-```
+#### Before submitting an enhancement suggestion
+
+- Check that your issue does not already exist in the issue tracker on GitHub.
 
-If you are using Linux or MacOS, you can make use of Makefile command `make tests`, which is a shortcut for the above python command.
+#### How do I submit an enhancement suggestion?
 
-You can also test on several python environments by using tox.
+Enhancement suggestions are tracked on the project's issue tracker on GitHub
+where you can create a new one and provide the following information:
 
-### Running tox on virtualenv
+- **Use a clear and descriptive title** for the issue to identify the
+  suggestion.
+- **Provide a step-by-step description of the suggested enhancement** in as many
+  details as possible.
+- **Provide specific examples to demonstrate the steps**.
+- **Describe the current behavior** and **explain which behavior you expected to
+  see instead** and why.
 
-Install tox:
+### Contributing to code
 
-```console
-pip install tox
+> This section is about contributing to
+[`graphql-server`](https://github.com/graphql-python/`graphql-server`).
+
+#### Local development
+
+You will need `uv` to start contributing to `graphql-server`. Refer to the
+[documentation](https://docs.astral.sh/uv/) to start using `uv`.
+
+You will first need to clone the repository using `git` and place yourself in
+its directory:
+
+```shell
+$ git clone [email protected]:graphql-python/`graphql-server`.git
+$ cd `graphql-server`
 ```
 
-Run `tox` on your virtualenv (do not forget to activate it!) and that's it!
+Now, you will need to install the required dependencies for ``graphql-server`` and be sure
+that the current tests are passing on your machine:
 
-### Running tox on Conda
+```shell
+$ uv sync --group integrations
+```
 
-In order to run `tox` command on conda, install
-[tox-conda](https://github.com/tox-dev/tox-conda):
+Some tests are known to be inconsistent. (The fix is in progress.) These tests are marked with the `pytest.mark.flaky` marker.
 
-```sh
-conda install -c conda-forge tox-conda
+`graphql-server` uses the [black](https://github.com/ambv/black) coding style and you
+must ensure that your code follows it. If not, the CI will fail and your Pull Request will not be merged.
+
+To make sure that you don't accidentally commit code that does not follow the
+coding style, you can install a pre-commit hook that will check that everything
+is in order:
+
+```shell
+$ uv run pre-commit install
 ```
 
-This install tox underneath so no need to install it before.
+Your code must always be accompanied by corresponding tests. If tests are not
+present, your code will not be merged.
+
+#### Pull requests
+
+- Be sure that your pull request contains tests that cover the changed or added
+  code.
+- If your changes warrant a documentation change, the pull request must also
+  update the documentation.
+
+##### RELEASE.md files
 
-Then uncomment the `requires = tox-conda` line on `tox.ini` file.
+When you submit a PR, make sure to include a RELEASE.md file. We use that to automatically do releases here on GitHub and, most importantly, to PyPI!
+
+So as soon as your PR is merged, a release will be made.
+
+Here's an example of RELEASE.md:
+
+```text
+Release type: patch
+
+Description of the changes, ideally with some examples, if adding a new feature.
+```
 
-Run `tox` and you will see all the environments being created and all passing tests. :rocket:
+Release type can be one of patch, minor or major. We use [semver](https://semver.org/), so make sure to pick the appropriate type. If in doubt feel free to ask :)

.github/workflows/tests.yml

@@ -1,6 +1,8 @@
-The MIT License (MIT)
+MIT License
 
-Copyright (c) 2017-Present Syrus Akbary
+Copyright (c) GraphQL Contributors (GraphQL.js)
+Copyright (c) 2018 Patrick Arminio (Strawberry)
+Copyright (c) Syrus Akbary (GraphQL Server)
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal