Client formatting hooks #187
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reorganize formatting hooks (composition mergers, error formatters, etc) into a concern that can be added to various objects. All output formatting methodology is now centralized on one object, and allows
Clientto be that object.Breaking changes
description_mergercomposer option. Overridemerge_descriptionsclient method.deprecation_mergercomposer option. Overridemerge_deprecationsclient method.default_value_mergercomposer option. Overridemerge_default_valuesclient method.directive_kwarg_mergercomposer option. Overridemerge_kwargsclient method.root_field_location_selectorcomposer option. Useroot_entrypointscomposer option.on_errorhook no longer populates GraphQL error message. Overridebuild_graphql_errorclient method to build the desired error shape.