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
Client
to be that object.Breaking changes
description_merger
composer option. Overridemerge_descriptions
client method.deprecation_merger
composer option. Overridemerge_deprecations
client method.default_value_merger
composer option. Overridemerge_default_values
client method.directive_kwarg_merger
composer option. Overridemerge_kwargs
client method.root_field_location_selector
composer option. Useroot_entrypoints
composer option.on_error
hook no longer populates GraphQL error message. Overridebuild_graphql_error
client method to build the desired error shape.