Make suffix of generated query response types customizable #2116
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.
This PR addresses the following issue: #2110
I made changes to
base-documents-visitor
that allow users to specify (via config) a custom suffix of generated operation result type names (likePlayerQuery
orPlayerMutation
types). Adding a suffixResult
to e.g.PlayerQuery
type would generatePlayerQueryResult
.To add a suffix (which type is
string
), you have to useoperationResultSuffix
inconfig.yml
.