@@ -101,28 +101,40 @@ input GalleryInput {
101
101
102
102
You might wonder why this is expressed as a directive in SDL rather than
103
103
explicitly having a new type keyword ; Brad Baker , contributor to GraphQL -Java ,
104
- summed it up in [ this comment back in
105
- 2023](https ://github .com /graphql /graphql -spec /pull /825#issuecomment-1659900665):
104
+ summed it up in
105
+ [ this comment back in 2023](https ://github .com /graphql /graphql -spec /pull /825#issuecomment-1659900665):
106
106
107
107
> use of the directive means that :
108
108
>
109
109
> - it 's minimally invasive in terms of SDL tooling that might be out there ,
110
110
> - it's minimally invasive in terms of Introspection,
111
- > - it's minimally invasive in terms of engine implementation, it proved quite easy to implement in graphql-java.
111
+ > - it's minimally invasive in terms of engine implementation, it proved quite
112
+ > easy to implement in graphql-java.
112
113
>
113
114
> Great stuff!
114
115
115
116
Since then there have been a number of reports of success :
116
117
117
- > I 'm very happy with where this landed . We 'd use it internally at my company . -- [Ethan Resnick ](https ://github .com /graphql /graphql -spec /pull /825#issuecomment-2128262620)
118
+ > I 'm very happy with where this landed . We 'd use it internally at my company .
119
+ > --
120
+ > [Ethan Resnick ](https ://github .com /graphql /graphql -spec /pull /825#issuecomment-2128262620)
118
121
119
- > More positive feedback : We are using it at HubSpot through the graphql -java implementation and look forward to it becoming standardized . -- [Henry Q . Dineen ](https ://github .com /graphql /graphql -spec /pull /825#issuecomment-2128324080)
122
+ > More positive feedback : We are using it at HubSpot through the graphql -java
123
+ > implementation and look forward to it becoming standardized . --
124
+ > [Henry Q . Dineen ](https ://github .com /graphql /graphql -spec /pull /825#issuecomment-2128324080)
120
125
121
- > I implemented support for OneOf input objects for the Caliban GraphQL library (Scala ) [...] it 's been fairly straightforward implementing support for it and I couldn 't really identify any areas that could have been improved . -- [kyri -petrou ](https ://github .com /kyri -petrou )
126
+ > I implemented support for OneOf input objects for the Caliban GraphQL library
127
+ > (Scala ) [...] it 's been fairly straightforward implementing support for it and
128
+ > I couldn 't really identify any areas that could have been improved . --
129
+ > [kyri -petrou ](https ://github .com /kyri -petrou )
122
130
123
- > We have been eagerly waiting at Jobber for this to land as well . [...] We have many use cases internally for it and we 're very excited to see this land ! -- [Clinton Pahl ](https ://github .com /graphql /graphql -spec /pull /825#issuecomment-2135724148)
131
+ > We have been eagerly waiting at Jobber for this to land as well . [...] We have
132
+ > many use cases internally for it and we 're very excited to see this land ! --
133
+ > [Clinton Pahl ](https ://github .com /graphql /graphql -spec /pull /825#issuecomment-2135724148)
124
134
125
- > Colleagues at work (Atlassian ) have been really happy with @oneOf , works exactly as you want it to and I haven 't heard any negative feedback . -- [Donna Zhou ](https ://github .com /dondonz )
135
+ > Colleagues at work (Atlassian ) have been really happy with @oneOf , works
136
+ > exactly as you want it to and I haven 't heard any negative feedback . --
137
+ > [Donna Zhou ](https ://github .com /dondonz )
126
138
127
139
## Availability
128
140
0 commit comments