We need to think about how to handle errors. Currently any error thrown on the serverside will be sent to the client over GraphQl. This may be helpful during development, but in a production environment you might not want to disclose sensitive information such as error messages or stack traces. This needs to be handled in a way that's flexible enough to transport errors during development but can be configured to suppress errors, e.g. in production
We need to think about how to handle errors. Currently any error thrown on the serverside will be sent to the client over GraphQl. This may be helpful during development, but in a production environment you might not want to disclose sensitive information such as error messages or stack traces. This needs to be handled in a way that's flexible enough to transport errors during development but can be configured to suppress errors, e.g. in production