I think the errorFormatter property of the controller is customisable.

Damian R

I'd rather prevent that one and send a validation error

Damian R

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? 😛

🤯 (1)

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 seems to need the authentication on the front end


Just make it work from the front end (yes, it's a dev environment :-)