Return GraphQLError instead of objects

[michenly]

WHY are these changes introduced?

Apply better error logging from storefront API to Customer Account API

[michenly]

not use

[frandiox]

Thanks!

Curious, why would you consider this a breaking change? The fact we are logging errors shouldn't break anything, no? Just more useful "noise" in the terminal.

We are changing the returned stuff to be a class instance instead of an object but I think that would only break if you do weird stuff with it 🤔

[michenly]

hi @frandiox I made it a breaking change because we are manipulating the message being return in the error.
It can break if the merchant is doing string comparison for the error to determine how to act on it. (which is something I did for not login error before introducing our own utility)

However, upon reflection, since it is sorta a grey area on if the string manipulation would constitute a breaking change. But our next release is not till April. I do think merging this and see if any weird breakage occur is the pragmatic call for now.