feat: extend shared types mechanism to include response types #1
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.
📝 Description
This PR extends the existing shared types mechanism in the GraphQL client generator to include response types, addressing duplication of identical response types across different operations.
Key Changes:
responseTypeSignaturescache to track response types across all operations.responsespackageHow it works:
${packageName}.responsespackageImplementation Details:
.inputsand.enumspackages and including operation-specific packagesTesting:
Areas for Review:
responseTypeSignaturesmap.responses) and potential conflictsLink to Devin run: https://app.devin.ai/sessions/443221ec4fc34abdae8cd3bf80457725
Requested by: @akkp-windsurf
🔗 Related Issues
This implements Step 1 of extending the shared types mechanism as described in the task requirements - comparing response types structurally and sharing identical ones across operations.