Middlware / other to record schema type of response

[joelcollinsdc]

If I have a mutation that has a response schema of UnionShape1Shape2Shape3 (sort of like UnionSuccessTypeFailureTypeErrorsType), and I want to log out for any query / mutation, which concrete type the response was... would a custom middleware be the right thing for this? How does one get access to the response schema in middleware?

[oojacoboo]

Back up a bit here and tell us your overall goals. It sounds like you want to invalidate a session based on an error, and then return a custom response. Is that correct?

[oojacoboo]

Why do you want to do that? It'd be more helpful if you stepped back and stated your overall goals, instead of your solution you've come up with. This is not the correct way to record errors. That should be done with your exception handler.

[joelcollinsdc]

I'm stating the requirement that I have to implement based on my project. My understanding is the exception handling process doesn't allow for custom schema defitnitions in the response.

[oojacoboo]

What do you mean by custom schema definitions in the response? You may be stating what you actually need, or you may be stating the solution you've come up with based on your limited knowledge.

[joelcollinsdc]

Heres some psudeocode of what Im trying to do

#[Mutation]
	public function createFoo(
	CreateFooInput $createFooInput
): FooCreatedOutput | FailedToCreateFooOutput | ValidationErrors {
	if (!isValid()) {
		Logger::setParam('responseType', ValidationErrors::class);
		return new ValidationErrors(['example']);
	}


	try {
		$foo = new Foo();
		Logger::setParam('responseType', FooCreatedOutput::class);
		return new FooCreatedOutput('success!');
	} catch (\Throwable) {
		Logger::setParam('responseType', FailedToCreateFooOutput::class);
		return new FailedToCreateFooOutput();	
	}
}

What I was hoping to figure out is how to set responseType automatically

[oojacoboo]

Right, you're doing this all wrong. You need to be using your global Exception handler for handling exceptions. There is no reason to use a try/catch block here. And your output type on this mutation, could just be FooCreatedOutput, or something more generic, but useful. Often people will just return an ID of the newly created entity.

https://www.php.net/manual/en/function.set-exception-handler.php

Use this function to set your callable for all exceptions and return a more uniform response. Logging can be done there as well.