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
For historical reasons, a lot of the apollo-smith codebase is based on the parser. Now that the compiler is stabilising, we can unify the apollo-compiler and apollo-smith GraphQL representations, instead of having to maintain yet another one. Ideally, each type generation by the DocumentBuilder would output apollo-compiler types, rather than the custom apollo-smith type, e.g. this function here returns an apollo-smith representations that we then maintain separately. This can be ast::Arugment instead.
The text was updated successfully, but these errors were encountered:
For historical reasons, a lot of the
apollo-smith
codebase is based on the parser. Now that the compiler is stabilising, we can unify theapollo-compiler
andapollo-smith
GraphQL representations, instead of having to maintain yet another one. Ideally, each type generation by theDocumentBuilder
would outputapollo-compiler
types, rather than the customapollo-smith
type, e.g. this function here returns an apollo-smith representations that we then maintain separately. This can beast::Arugment
instead.The text was updated successfully, but these errors were encountered: