René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Return POJO instead of LinkedHashMap","articleBody":"Dear all,\r\nI'm trying to use graphql-java for loading a graph of in-memory java objects and doing some transformations on them (e.g. exporting to CSV). \r\nWhen I use `graphql.execute(ExecutionInput)`, it always provides a list of nested `LinkedHashMap`s\r\nHowever, I would prefer having results as POJOs.\r\n\r\nI dig a little bit into the code, and found, that the results are aggregated in `AbstractAsyncExecutionStrategy#handleResults`. So I decided to implement a custom strategy, which would build POJO directly.\r\nHowever, I don't see any way, how to know, which output class it should be. I could take it from the current `ExecutionPath` (which is available in `ExecutionStrategyParameters`), but `handleResults` doesn't have this parameter.\r\n\r\nSo, my questions are:\r\n1. Is there any way to get current ExecutionPath in `handlerResults`?\r\n2. Is there any other way to produce POJO instead of LinkedHashMap?\r\n\r\nPS thanks a lot for the wonderful library!","author":{"url":"https://github.com/bugy","@type":"Person","name":"bugy"},"datePublished":"2020-04-10T13:22:57.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":7},"url":"https://github.com/1855/graphql-java/issues/1855"}