You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: rfcs/InputUnion.md
+30-7Lines changed: 30 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -128,9 +128,38 @@ In this mutation, we encounter the main challenge of the **Input Union** - we ne
128
128
129
129
A wide variety of solutions have been explored by the community, and they are outlined in detail in this document under [Possible Solutions](#Possible-Solutions).
130
130
131
+
132
+
## Prior Art
133
+
134
+
Many other technologies provide polymorphic types, and have done so using a variety of techniques.
*[C2 Wiki: Nominative And Structural Typing](http://wiki.c2.com/?NominativeAndStructuralTyping)
158
+
159
+
131
160
## Solution Criteria
132
161
133
-
Hypothetical goals that a solution might attempt to fulfill. These goals will be evaluated with the [GraphQL Spec Guiding Principles](https://github.com/graphql/graphql-spec/blob/master/CONTRIBUTING.md#guiding-principles) in mind:
162
+
This section sketches out the potential goals that a solution might attempt to fulfill. These goals will be evaluated with the [GraphQL Spec Guiding Principles](https://github.com/graphql/graphql-spec/blob/master/CONTRIBUTING.md#guiding-principles) in mind:
134
163
135
164
* Backwards compatibility
136
165
* Performance is a feature
@@ -212,12 +241,6 @@ There have been a variety of use cases described by users asking for an abstract
0 commit comments