Unhandeled CastError in dataloader #911
chladog
started this conversation in
Feature Requests & Ideas
Replies: 2 comments 3 replies
-
I just found out that this error also happens when querying object that has relationship field reference to an object that doesn't exist anymore and it tries to query it (when depth > 0) This should be moved to Issues. |
Beta Was this translation helpful? Give feedback.
3 replies
-
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I encoutered following error already with #884 which since then was fixed.
Now the topic is regarding an error handling of this error. Sometimes I get this error, probably because of old invalid type data in my mongodb. Ofc invalid data shouldn't get stored in DB in the first place, but it happens - in this particular case it was a saved JSON in the relationship field where only ID should be stored.
The problem is that this error currently 1) kills the server process 2) therefore breaks whole GQL request so it's not possible to generate at least partial view with valid data and displaying an error to user.
Could this be handled the way that as much of valid data is returned back along with error message reporting the field of the problem so it doesn't break the app UX?
Beta Was this translation helpful? Give feedback.
All reactions