e.g. ```instances(className: "com.squareup.exampl...

# kgraphql

[py]

e.g.

instances(className: "com.squareup.example.Foo") {
  someField
  someOtherField  
}

[jeggy]

As GraphQL is strictly typed by definition, it is a bit hard to have dynamic fields like this.
But I have seen other GraphQL implementations have support for JSON data type. This could be something that KGraphQL should also have support for.

[jeggy]

But you can easily create a base class and then have something like this:

type<Foo> {
  property<String>("someField") {
    resolver { "Value to return" }
  }
  property<String>("someOtherField") {
    resolver { "Other value to return" }
  }
}

[py]

interesting, I need to think about this. I was basically thinking that the parameters provided would help locate the type and its fields.

On the other hand, I might be able to work around that by registering all known classes in the heap dump on start, and do what you just suggested.

[jeggy]

I'm not really sure what your "heap dump" is. But if these are some random document data structure, then it will probably be a bit hard getting them into GraphQL types. But most likely those types have some specific class structure and it's just the matter of returning them correctly

[py]

A heap dump is a copy of the java heap. Classes, instances, etc.

[jeggy]

I'm not sure what structure or how you would get that information into your Kotlin code.
But I guess it can be in a String format.

So you could create a GraphQL scalar for it using stringScalar and then where ever you use your graphql service, you can deserialize it however you want.

[py]

thx, I’ll play again with it when they fix the compose bug 🙂

[py]

(but yeah anyway that information presents itself in the form of the API I wrote for the heap dump parser, which is somewhat similar to Java reflection APIs)