Hello! If I understand correctly, you’d like to reuse a query that includes fields that you sometimes don’t want to query for. Yes, you can approximate this behavior.
In your resolver for isLocationOf, you can check the value of includeChild. If it’s false, you can add a corresponding boolean flag to the shared context argument.
Then, in the resolver for node (or whatever field you want to selectively exclude), first check context to see if that flag has been set. If it has, return null instead of what you would return otherwise.
Note that for this to work, the field you want to selectively exclude must be nullable in your schema.