Skip to content
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

GraphQL 4 Compatability #293

Closed
wants to merge 21 commits into from

Conversation

unclecheese
Copy link

No description provided.

@unclecheese unclecheese force-pushed the pulls/1/schemageddon branch 2 times, most recently from e0cb01b to be90021 Compare August 5, 2020 03:08
@ScopeyNZ
Copy link
Contributor

ScopeyNZ commented Aug 5, 2020

Can you leave all the old stuff and manage to keep compatibility with GraphQL <4. As it stands, all these removals of classes cannot happen without a major release.

@unclecheese
Copy link
Author

Yup, fair point. I was just thinking that those classes rely on ancestors that won't exist anymore, but we can put class_exists() guards around them like the rest of the module. I'll move the deletion commits to the master branch.

composer.json Outdated
@@ -28,9 +28,6 @@
"silverstripe/admin": "^1",
"squizlabs/php_codesniffer": "^3"
},
"conflict": {
Copy link
Member

@sminnee sminnee Aug 16, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it be better to say "conflict: silverstripe/graphql >= 5"? Or maybe >= 5 || <3?

@unclecheese unclecheese force-pushed the pulls/1/schemageddon branch 6 times, most recently from e08d67c to fc338de Compare November 2, 2020 00:23
@unclecheese unclecheese marked this pull request as ready for review November 2, 2020 00:23
@unclecheese unclecheese force-pushed the pulls/1/schemageddon branch 6 times, most recently from 32dad8a to 54d0b0e Compare November 2, 2020 01:03
@unclecheese
Copy link
Author

Moved to: #308

@unclecheese unclecheese closed this Nov 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants