-
Notifications
You must be signed in to change notification settings - Fork 34
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
Conversation
e0cb01b
to
be90021
Compare
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. |
Yup, fair point. I was just thinking that those classes rely on ancestors that won't exist anymore, but we can put |
composer.json
Outdated
@@ -28,9 +28,6 @@ | |||
"silverstripe/admin": "^1", | |||
"squizlabs/php_codesniffer": "^3" | |||
}, | |||
"conflict": { |
There was a problem hiding this comment.
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?
7e3ebfb
to
d1a75b4
Compare
68736db
to
46aa27d
Compare
e08d67c
to
fc338de
Compare
32dad8a
to
54d0b0e
Compare
54d0b0e
to
61b8e99
Compare
Moved to: #308 |
No description provided.