GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||||||||||
GeezerVison is showing github.com — Retriveing singleton property fetchers will not create DataFetcherFactoryEnvironment objects by bbakerman · Pull Request #3942 · graphql-java/graphql-java Conversation
|
| public DataFetcher<Object> get(GraphQLFieldDefinition fieldDefinition) { | ||
| return SINGLETON_FETCHER; | ||
| } | ||
| }; |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
because I didnt override the default public DataFetcher<Object> get(GraphQLFieldDefinition fieldDefinition) then it returned null and hence it went to the older more heavy weight object and a DataFetcherFactoryEnvironment needed to be allocated.
This now means that no DataFetcherFactoryEnvironment objects are allocated for property fetchers
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I cant unit test this - its not observable - but profiling shows it to be working!
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Nice you could verify via profiling
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Test Results 312 files 312 suites 53s ⏱️ Results for commit ade6100. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.