Using Anonymous Objects to Define the Response Type

I am just starting to experiment with graphql and the graphql.client and have a pretty straight-forward mutation to add a new user:

```
mutation CreateTheUser($input: CreateUserInput!) {
createUser(input: $input) { createUserResult {newUser {id, name}, errorMessage }}
}
```

With variables as below:

```
{
"input": {
"name": "Fred",
"securityLevel": 30}
}

```
This gives me back json like this:

```
{
"data": {
"createUser": {
"createUserResult": {
"newUser": {
"id": 626,
"name": "Fred"
},
"errorMessage": null
}
}
}

```
So if I want to get my hands on a CreateUserResult (the third level in), am I right to define a responseDefinition like below? I have seen people use an anonymous object to go one level below Data...so is there anything wrong with going two down? Or am I making things more complicated than they need to be?

```
public async Task CreateUser(CreateUserInput input)
{
GraphQLRequest request = new()
{
Query = @"
mutation CreateUser($input: CreateUserInput!) {
createUser(input: $input) { createUserResult {newUser {id, name}, errorMessage }}
}",
Variables = new { input }
};
var responseDefinition = () => new { CreateUser = new { CreateUserResult = new CreateUserResult() } };
var response = await _graphQLClient.SendMutationAsync(request, responseDefinition);
return response.Data.CreateUser.CreateUserResult;
}

```

Thanks for any input
Fletcher