[Platform.sh] Inline document support for GraphQL#388
[Platform.sh] Inline document support for GraphQL#388janit wants to merge 12 commits intoezsystems:2.5from janit:master
Conversation
Instead of defaults, they are now options if you want/need to deploy Schema updates.
|
@bdunogier Maybe you can take over on this? @janit is on mission, and me and @vidarl is on easter holliday. |
|
Thanks @bdunogier , from what I can gather then we should not adapt platform.sh config like this, but rather start to check in the schema file on /cc @damianz5 & @SylvainGuittard |
|
As for demo, @andrerom, if we consider it as a standard project (e.g. not the headless case where you never touch the config / templates), then yes, it is what we should do. |
This would be a good option for the time being. There is a drawback though: it implies that we version the schema files, meaning that they would show up as modified when the script is executed. Alternatively, we could make that step part of the installer, and copy the schema files to the schema directory on install. As a bonus, we would be sure that the schema matches the install type, since it would come with it. A short-term alternative is to make the schema files writable in The long-term solution is to make the GraphQL schema fully dynamic (e.g. updated whenever content types / config is modified). (Much) more complex. |
eZ Platform v2.5 supports GraphQL by default. To enable support also on eZ Platform Cloud / Platform.sh the following changes are needed:
app/config/graphqlphp bin/console ezplatform:graphql:generate-schemaNote that this will NOT enable the commonly used GraphiQL client in
prodenv mode. In fact, because of the--no-devflag used for composer, the GraphiQL package will not work even indevenv.