Support skipping readonly fields

Product

Hot Chocolate

Is your feature request related to a problem?

We have a class generated from XSD. This class include generated fields like XXSpecified, which are mandatory to XmlSerializer. For example:

/// <summary>
/// <para xml:lang="en">Gets a value indicating whether the Error collection is empty.</para>
/// </summary>
[XmlIgnoreAttribute()]
public bool ErrorSpecified
{
    get
    {
        return (this.Error.Count != 0);
    }
}

Once we use this class as an Input type, HotChocolate will complain that the XXSpecified fields are read-only. Can we have options to allow skipping read-only fields?

The solution you’d like

Read-only fields are automatically skipped when using as Input.

[xionglingfeng]

Yes. I would expect HotChocolate to skip this field when generating schema for MyInputClassInput. However, the field can be kept when generating schema for MyInputClass (not Input).

This read-only field is actually expected when using the class as a return type. Thus I cannot apply [GraphQLIgnore].

[michaelstaib]

In this case the GraphQL schema would be invalid as the input would end up with no fields which is not allowed by the GraphQL spec. What you can do is specify type configurations that describe the input and output behavior.

services
    .AddGraphQLServer()
    .AddInputType<MyInputClass>(t => t.Ignore(d => d.Names));

If you have multiple of these you can override the DefaultTypeInspector and ignore these on input. But as I said, it will fail if the input ha no other fields.