We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hot Chocolate
When an entity key includes fields of fields, the ArgumentParser fails if any object type fields are required.
ArgumentParser
schema:
type Entity @key(fieldset: "type detail { id }") { id: ID! type: EntityType! detail: Detail! } enum EntityType { TYPE_A TYPE_B } type Detail { id: ID! }
[ReferenceResolver] public static Entity Resolve(EntityType entityType, [Map("detail.id")] string detailId) ....
detailId will always be null, with no error from the pipeline
detailId
However if Entity is defined as:
Entity
type Entity @key(fieldset: "type detail { id }") { id: ID! type: EntityType! detail: Detail }
where detail is optional, then it works.
detail
No response
Somewhat related to #6232 , only in this case it's the IType parameter that isn't being properly handled.
IType
If type is NonNullType it fails the type check at
type
if (type is not IComplexOutputType complexType || !complexType.Fields.TryGetField(current, out var field))
13.5.1
The text was updated successfully, but these errors were encountered:
Fixes ChilliCream#6594
4b87d2d
a02a1b7
Successfully merging a pull request may close this issue.
Is there an existing issue for this?
Product
Hot Chocolate
Describe the bug
When an entity key includes fields of fields, the
ArgumentParser
fails if any object type fields are required.Steps to reproduce
schema:
detailId
will always be null, with no error from the pipelineHowever if
Entity
is defined as:where
detail
is optional, then it works.Relevant log output
No response
Additional Context?
Somewhat related to #6232 , only in this case it's the
IType
parameter that isn't being properly handled.If
type
is NonNullType it fails the type check atVersion
13.5.1
The text was updated successfully, but these errors were encountered: