Replies: 1 comment 6 replies
-
|
THIS!!! This is absolutely killing me. I have a calculated field implemented as a custom field resolver. It depends on information from two navigation properties over. Those objects do not appear in the query itself, so those objects are never loaded. When the custom field resolver tries to run, they are null. Under v13 they were lazy-loading proxies and things just worked. It wasn't as efficient, but it worked. I am trapped on v13 until I can solve this. After multiple efforts to solve this myself, I have unleashed a Claude Opus instance will full autonomy to try to solve this. It has run for hours every day off to the side, silently trying and failing to come up with a viable workaround. Every proposed solution fixes something at the expense of something else. My current idea is to just say "screw it" in the custom field resolver, grab the context and do it myself just so that we can update to v14/v15/v16 in the hope that somehow this will be possible in the future, but I can't make it past step 1. Just make my code WORK in v14. I WANT to update this code. I WANT to fix this problem in a more proper way. But I can't. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everybody. I have a problem with HotChocolate Projection and hope somebody can help me with that.
In my query I added the following attributes (also the attribute UseProjection)
Additionally I have resolvers like this which works perfectly fine as long I mark the field DateOfBirth as IsProjected or ask for the field DateOfBirth in the query.
No to the problem. If I have a calculated field by a resolver which uses another table (foreign key navigation). Then the IsProjected does not work properly. When I don't ask for the navigated field PersonComments.
Does anybody know this problem.
Beta Was this translation helpful? Give feedback.
All reactions