A more memory efficient AstPrinter by bbakerman · Pull Request #4028

A more memory efficient AstPrinter by bbakerman · Pull Request #4028 · graphql-java/graphql-java

Test Results

318 files - 632 318 suites - 632 2m 46s ⏱️ - 5m 39s
4 884 tests - 312 4 874 ✅ - 313 10 💤 + 1 0 ❌ ±0
4 973 runs - 9 940 4 963 ✅ - 9 921 10 💤 - 19 0 ❌ ±0

Results for commit 83ec4d5. ± Comparison against base commit aef8032.

This pull request removes 462 and adds 128 tests. Note that renamed tests count towards both.

	?
                __schema { types { fields { args { type { name fields { name }}}}}}
                __schema { types { fields { type { name fields { name }}}}}
                __schema { types { inputFields { type { inputFields { name }}}}}
                __schema { types { interfaces { fields { type { interfaces { name } } } } } }
                __schema { types { name} }
                __type(name : "t") { name }
                a1: __schema { types { name} }
                a1: __type(name : "t") { name }
                a2 :  __type(name : "t1") { name }
…

graphql.ScalarsBooleanTest ‑ parseValue throws exception for invalid input <java.lang.Object@236f1f73>
graphql.ScalarsBooleanTest ‑ serialize throws exception for invalid input <java.lang.Object@5400402d>
graphql.ScalarsIDTest ‑ parseValue allows any object via String.valueOf <java.lang.Object@186b53de>
graphql.ScalarsIDTest ‑ serialize allows any object via String.valueOf <java.lang.Object@3109b25e>
graphql.ScalarsIntTest ‑ parseValue throws exception for invalid input <java.lang.Object@3452f5e6>
graphql.ScalarsIntTest ‑ serialize throws exception for invalid input <java.lang.Object@74ccba17>
graphql.execution.instrumentation.TracingInstrumentationTest ‑ do not trace introspection information [testExecutionStrategy: <graphql.execution.AsyncExecutionStrategy@78fa1c7e fieldCollector=graphql.execution.FieldCollector@16226377 executionStepInfoFactory=graphql.execution.ExecutionStepInfoFactory@68eb2246 dataFetcherExceptionHandler=graphql.execution.SimpleDataFetcherExceptionHandler@18f531b9 resolvedType=graphql.execution.ResolveType@30c4d735>, #0]
graphql.execution.instrumentation.TracingInstrumentationTest ‑ do not trace introspection information [testExecutionStrategy: <graphql.execution.AsyncSerialExecutionStrategy@4b0ce7a fieldCollector=graphql.execution.FieldCollector@35f94fac executionStepInfoFactory=graphql.execution.ExecutionStepInfoFactory@23124b59 dataFetcherExceptionHandler=graphql.execution.SimpleDataFetcherExceptionHandler@57821091 resolvedType=graphql.execution.ResolveType@55c3c705>, #1]
graphql.execution.instrumentation.TracingInstrumentationTest ‑ tracing captures timings as expected [testExecutionStrategy: <graphql.execution.AsyncExecutionStrategy@5acd6f1c fieldCollector=graphql.execution.FieldCollector@3c87551b executionStepInfoFactory=graphql.execution.ExecutionStepInfoFactory@711d977f dataFetcherExceptionHandler=graphql.execution.SimpleDataFetcherExceptionHandler@55cba574 resolvedType=graphql.execution.ResolveType@64cf855e>, #0]
graphql.execution.instrumentation.TracingInstrumentationTest ‑ tracing captures timings as expected [testExecutionStrategy: <graphql.execution.AsyncSerialExecutionStrategy@187b6d97 fieldCollector=graphql.execution.FieldCollector@ee8d0a5 executionStepInfoFactory=graphql.execution.ExecutionStepInfoFactory@41f022de dataFetcherExceptionHandler=graphql.execution.SimpleDataFetcherExceptionHandler@5ef759ab resolvedType=graphql.execution.ResolveType@1d238037>, #1]
…

This pull request skips 1 test.

graphql.schema.fetching.LambdaFetchingSupportTest ‑ different class loaders induce certain behaviours

xuorig left a comment •

Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

As an aside:

It could be great to add an API that allows users to pass their own string builder for flexibility. That allows things like reserving the capacity needed, or reusing string builders, which we both currently do in a custom printer.

    public static StringBuilder printAst(Node node, StringBuilder out) {
        printAstTo(node, out);
        return out
    }

Thank you!

As an aside:

It could be great to add an API that allows users to pass their own string builder for flexibility. That allows things like reserving the capacity needed, or reusing string builders, which we both currently do in a custom printer.
    public static StringBuilder printAst(Node node, StringBuilder out) {
        printAstTo(node, out);
        return out
    }

We have

    public static void printAstTo(Node<?> node, Appendable appendable) {

and StringBuilder is an Appendable so thats already possible

StringBuilder out = new StringBuilder();
AsPrinter.printAstTo(node1,out);
AsPrinter.printAstTo(node2,out);

out.append("more strings")

Maybe not super fluent but possible

Test Results

xuorig left a comment • Loading

Choose a reason for hiding this comment

xuorig left a comment •

Loading