Similar to #681, @field directive can be provided with Type information in a string form, which will then need to be parsed before being used in the schema. It seems like it does not need to be validated specifically (but we should do it anyways)
To make this change, we need to:
add parse_type method to apollo-parser
add a cst::Type specific method for SyntaxTree implementation to return the CST node, similar to doc.document(), and field_set.field_set()
create a parse_type method in apollo-compiler
add Type struct to apollo-compiler's schema that would also be able to include BuildErrors
add a parse and validate methods to the Type struct impl
Similar to #681,
@fielddirective can be provided withTypeinformation in a string form, which will then need to be parsed before being used in the schema. It seems like it does not need to be validated specifically (but we should do it anyways)To make this change, we need to:
parse_typemethod toapollo-parsercst::Typespecific method forSyntaxTreeimplementation to return the CST node, similar to doc.document(), and field_set.field_set()parse_typemethod inapollo-compilerTypestruct toapollo-compiler's schema that would also be able to includeBuildErrorsparseandvalidatemethods to theTypestruct impl