You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When resolvers are specified for a field via fieldsWithResolver, the field is excluded from the object being generated
When resolvers are not specified, the field is included in the object being generated
The problem
Adding ad-hoc resolvers that are outside the plugin scope is impossible because the field will always be generated.
Use case: if I want to add a custom @BatchMapping resolver it will either conflict with the "singular" one generated by the plugin or, if resolver generation is disabled we will end up with the field in the object that we don't want
Suggested solution
Add extra plugin option to allow excluding specified fields from generation, e.g.
Uh oh!
There was an error while loading. Please reload this page.
Current behaviour
fieldsWithResolver
, the field is excluded from the object being generatedThe problem
Adding ad-hoc resolvers that are outside the plugin scope is impossible because the field will always be generated.
Use case: if I want to add a custom
@BatchMapping
resolver it will either conflict with the "singular" one generated by the plugin or, if resolver generation is disabled we will end up with the field in the object that we don't wantSuggested solution
Add extra plugin option to allow excluding specified fields from generation, e.g.
Expected behavior:
fieldsExcludedFromGeneration
it is excluded from generation (not present within the object)fieldsExcludedFromGeneration
and infieldsWithResolver
it is excluded from generationfieldsExcludedFromGeneration
and infieldsWithoutResolver
it is excluded from generationThe text was updated successfully, but these errors were encountered: