Upon sending that mutation, no exception log is printed on the console but the GraphQL response is:
Value: [{territoryHead={login=1231rdq3re1d2c, name=User, phoneNumber=12345678}, counterNumber=1, ...}] could not be parsed into an instance of javolution.util.FastTable<CreateTerritoryDto>
Upon further investigation, I discovered that the issue was because the AppUser class did not have a default or no-argument constructor. This took a bit of time to discover and it was very easy to fix (by just adding @NoArgsConstructor lombok anotation on that class). It would have been easier to troubleshoot if the exception stack-trace was being printed on the console.
How can I enable printing of such data fetching exceptions?
Certain Exceptions occuring during DataFetching are not logged to the console. i.e. their stack-trace. For example, I have the following code:
And I was sending this mutation:
Upon sending that mutation, no exception log is printed on the console but the GraphQL response is:
Upon further investigation, I discovered that the issue was because the
AppUser
class did not have a default or no-argument constructor. This took a bit of time to discover and it was very easy to fix (by just adding@NoArgsConstructor
lombok anotation on that class). It would have been easier to troubleshoot if the exception stack-trace was being printed on the console. How can I enable printing of such data fetching exceptions?I've tried this but it doesn't help: