Bring something like strawberry-graphene into core

[patrick91]

I’ve been meaning to do this for a while, and I recently spoke with one of our sponsors. They’re migrating from Graphene to Strawberry, so having a compatibility layer for a recent version of Graphene would be particularly helpful.

John built a Strawberry–Graphene compatibility layer about five years ago. I think it’s worth bringing that into core. The folks I’ve spoken with are happy to open a pull request with their version, and we may be able to just use that since it’s already in use and appears to be working well.

From what I’ve seen in the code, I’d like to make a few changes to improve reusability for others.

Also, we could ship this as a separate package, but if it lives in core it’s easier to ensure that the compatibility-layer updates stay in sync with core changes. If it’s external, we’d need to remember to update it every time (and I'll forget for sure).

I’m opening this issue to make the proposal visible 😊

[XChikuX]

My vote:

Core - If compatability layer has low/none 3rd party dependencies
External - If it has too many 3rd party dependencies

[erikwrede]

I like the idea of bringing it right into this repo, as it forces us to keep up with any changes. However I'd like to see the PR first to be able to judge how intrusive to our core logic it might be.

[patrick91]

I like the idea of bringing it right into this repo, as it forces us to keep up with any changes. However I'd like to see the PR first to be able to judge how intrusive to our core logic it might be.

Ideally it wouldn't touch our core at all, but we'll see 😊