-
Notifications
You must be signed in to change notification settings - Fork 115
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
PHP8 support #866
Comments
Was looking to update a few of my sites to php8 and with 4.6.0 released currently it seems that only Silverstripe Elemental is the only module not fully supporting php8 yet. v4.3.2 works great with php8 so assuming its more the changes to graphql4 that need attention. Just wondering if this is on the roadmap this year or what can be done to help get this over the line |
I don't believe GraphQL 4 is a blocker in regards to PHP8 support. We're aiming to get PHP8 support across the board for modules that Silverstripe Ltd supports later this year. Currently most things should work fine with PHP8, though not everything. We haven't announced official support yet. |
4.6.0 broke compatibility with graphql 3 (see #870), now that graphql typeNames map is no longer respected. Can you update the composer dependencies to reflect that? graphql 3 users upgrading their silverstripe versions will need to lock to ~4.5.0 of elemental. |
OK that wasn't supposed to happen, elemental 4.6.0 should work on both versions of graphql. Thanks for pointing this out. |
banner-block should be sorted by this silverstripe/silverstripe-elemental-bannerblock#78 (comment) |
There's nothing left to do on this. |
ACs
4
are also merged before taggingTag 4.6.0 which also includes graphql4 supportThe text was updated successfully, but these errors were encountered: