Message of the day:
Anything GraphQL and SilverStripe related.
likes GraphQL. The same API, but not the hassle of REST or SOAP
I think the
errorFormatter property of the controller is customisable.
I'd rather prevent that one and send a validation error
Is there a way to catch the error caused by fields not being passed into a mutation? Currently the application 500s with a very unhelpful error message sent to front end
Time to upgrade a project. So, what's changed in silverstripe-graphql in the past year? 😛
Happily it still seems to run fine after updating all my composer deps
I'm hoping I can drop some of the weird hacks I had to do, like
I think there were better support for polymorphism in graphql, I don't remember the versions though
multi schema, versioning support, middleware api, CSRF protection
Massive API changes coming in the next major release, though (graphql 4.x, ss 4.5)
4.5 or 4.4?
@anton has joined the channel
Entirely depends on the version, JWT is broken in the latest I believe, Ingo made an issue about it which isn't resolved yet
it works really well 🙂
I am use the JWT module in my React apps FYI https://github.com/Firesphere/silverstripe-graphql-jwt
It seems to need the authentication on the front end
Just make it work from the front end (yes, it's a dev environment :-)