Should GraphQL resources support hierarchical path names for resources?

[ThisaruGuruge]

In GraphQL context, what is the meaning of a hierarchical path name for a resource?

GraphQL has resolvers that return either Scalar, Object or Enum.
Each resource function in a GraphQL service becomes a resolver itself. These resolvers have return types.

For example:

import ballerina/graphql;

service /graphql on new graphql:Listener(9090) {
    resource function get profile() returns Person {
        // ...
    }
}

The resource function profile is now become a field (selection) of the type queryType of the corresponding graphql schema. It has a return type of Person.

If we have a resource like this:

resource function get profile/name() returns string {
    // ...
}

What should be the type of the profile field? How can we infer this type?

Therefore, IMHO, we should not support hierarchical path names in GraphQL resources.

WDYT?
@shafreenAnfar