Message of the day:
Anything GraphQL and SilverStripe related.
likes GraphQL. The same API, but not the hassle of REST or SOAP
What if I told you declarative APIs aren't really declarative if they can be broken by order of execution?
Solved it, was because I had this in my api.yml
- - '#graphqlconfig'
Unknown column errors on
/dev/build because it's trying to execute queries in functions exposed via GraphQL, before the database changes has been build. Any one experienced the same?
it's convenient, but you don't have to use it to get it working
maybe include the dev-master recipe? or use the framework-recipe and install the modules manually? A recipe is nothing more than a meta package with a bunch of dependencies
but recipe-cms complains about it
you can make
3.2.x-dev as 3.1.4, if it's compatible
> silverstripe/recipe-cms 4.4.4 requires silverstripe/graphql [email protected]
Well, in the latest stable https://github.com/silverstripe/silverstripe-graphql/tree/3.1.4/src I don't see the permission folder. Maybe @unclecheese didn't release it yet? You can include "3.2.x-dev" with composer (according to https://packagist.org/packages/silverstripe/graphql#3.x-dev)
Serves SilverStripe data as GraphQL representations - silverstripe/silverstripe-graphql
GraphQL server for SilverStripe models and other data
GraphQL server for SilverStripe models and other dataHide attachment content
But this confuses me big time