StrawberryShake, nested fragments produces query-related interfaces

[Arsync]

Purpose: for using StrawberryShake-generated interfaces as guidlines to client-side models, created manually.

For example, we have domain models at server side like

public class HumanName
{
    public string Family { get; set; }
}

public class Person
{
    public HumanName Name { get; set; }
}

And query it with StrawberryShake like

query GetPerson($id: Int!) {
    person(id: $id) {
        ...PersonModel
    }
}

fragment NameModel on HumanName {
    family
}

fragment PersonModel on Person {
    name {
        ...NameModel
    }
}

It produces following code:

[global::System.CodeDom.Compiler.GeneratedCode("StrawberryShake", "13.0.5.0")]
public partial interface INameModel
{
    public global::System.String? Family { get; }
}

[global::System.CodeDom.Compiler.GeneratedCode("StrawberryShake", "13.0.5.0")]
public partial interface IGetPerson_Person_Name : INameModel
{
}

[global::System.CodeDom.Compiler.GeneratedCode("StrawberryShake", "13.0.5.0")]
public partial interface IPersonModel
{
    public global::Client.GraphQL.IGetPerson_Person_Name Name { get; }
}

Where the Name property implements query-based interface, not just INameModel. So we can't use IPersonModel to implement it in client-side model Person like Person : IPersonModel without relation to the specific query.

I think, I've conceptually wrong and there is another use for fragments. But after switching from OpenRiaServices, there is no such native client model autogeneration like before.

Found generated PersonEntity, but it looks like for internal StrawberryShake use in its store. Can we use such entities in business-logic scenarios?

[global::System.CodeDom.Compiler.GeneratedCode("StrawberryShake", "13.0.5.0")]
public partial class PersonEntity
{
    public PersonEntity(global::Client.GraphQL.State.HumanNameData name = default !)
    {
        Name = name;
    }

    public global::Client.GraphQL.State.HumanNameData Name { get; }
}

[Arsync]

Works pretty well with AutoMapper added on client side (Blazor Wasm), where we can create map from defined fragment to client model.