fix(ClientApiGenFragmentTestv2.kt): fragment name projection #549
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 change fixes an issue where the codegen results in two Projection generated objects that share the name when used for union types as well as field projections.
Example schema:
Because
Movie
is used both as a field and as a union type, when codegen generates projection objects for each, they will result in the sameMovieProjection
and only one file will be written to disk. What this change does is it renames the projection objects used in fragments, so that they can be written to disk separately.