GraphQL wildcard field about faq

[snlacks]

I feel this is ignoring the community. All three of those bullet points are refuted when we take into account that these are professional, experienced developers who have read those previous concerns elsewhere and still want the feature. This unhelpful, "it's for performance" is not a valid reason to exclude a feature, where it's a choice of the developer. It's for philosophy. If it were purely performance, there could be flags, warnings, or limits.

The consumer of persisted data and GraphQL may technically and philosophically be under the same control, but in actual use, organizational, knowledge domains, and practical matters often still keep these concerns separate. There's already explanation in comments, open issues, unanswered Stack Overflow questions, critical blog posts, and angry tweets that prove that there's an actual need, so I will leave it at that.

[benjie]

I don't think this is the place to argue one way or the other for the future of the feature in the GraphQL spec (that's what the spec repo is for). The fact is that GraphQL does not currently have wildcard fields and people frequently ask why not. The intent of this issue is to suggest that we should have a canonical answer to this frequently asked question, the most salient reason IMO being that it enables the versionless schema design and evolution that GraphQL encourages.

I have no problem with the answer linking to the discussion about the possibility of adding them in the future, but I think the FAQ should answer questions about the GraphQL specification as it stands.