WhiteGive

@kobylynskyi Yes correct. Based on my knowledge of the source code, the only change is to add getFields() in GraphQLResponseProjection.java

Sorry for the late reply. The "copy" constructor may not work. As the aim of creating from existed one is to get the fields from a projection so that the...

> We should not modify the original `getFields` There is no getFields() in current Graph l response projection. We are thinking of adding this methods to access and modify the...

> If the internal fields can be modified after creating object, it may lead to insecurity. Could you explain the insecurity case a bit more? about what scenario and what...

Hi @kobylynskyi , There are two comments on your idea: 1. The current response projection class does not support deduplication of fields. If we take your idea, the fields addition...

Hi @kobylynskyi , sorry for the late reply. I've consolidated the idea and let's take the below example: #### Suppose we have a GQL model ``` account: Account user: Person...

@kobylynskyi May I know if you have any plan to make code change and add this feature? otherwise I think I can contribute with a PR.

@kobylynskyi Thanks. I checked the code change. From my knowledge, GraphQL service could support duplicate field with different alias. For example, this query is supported, as the alias are different:...