-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG]: cryptic errors making hard to debug cycle or someething #232
Comments
NOTE: by the way, the lib has been super solid!!!!!!! thanks!!! All our apis are used by the angular client and by the server so our apis are 100% the same now so developers can easily read the contracts on either end since it is the same file for both server developer and GUI developer (though we are all full stack anyways). |
Ok, I tried deleting entire app to just focus on the api but that became a rabbit hole :( . full object heirarchy is
|
Hi, let me check, but could you provide the payload you try to deserialize so that I can check with real data? |
oh shoot, I lost that :(. I ended up doing a complete refactor and it fixed itself as the issue was in a part of the code where we had some big technical debt and I figured no better time than now since it has an issue. Perhaps you could add more detail to the exception through on any variable.name in the library code??? This is the 2nd time I ran into that one(though I have no idea if it was the same exact line of code). If in the lib we do a if(!variable) throw Error(more info), it will come into the next bug report as well much easier as people copy the stack traces. |
Version
6.0.0
Description
I suspect a cycle but can't find it. In guice, on errors, it would report the cycle, A, B, C, A so you could fix. Perhaps this is a feature request though I think it is more a usability bug costing time every time we hit it. if you have a debug process that would be amazing. I changed my entity to this code adding {type: ProposalDto} and things broke :( ....
Error
The text was updated successfully, but these errors were encountered: