apollographql / apollo-rs Goto Github PK

• parse OperationDefinition
• parse OperationType
• parse OperationTypeDefinition

• parse Value
• parse StringValue (in lexer)
• parse FloatValue (in lexer)
• parse IntValue (in lexer)
• parse BooleanValue (in lexer)
• parse NullValue
• parse EnumValue
• parse ListValue
• parse ObjectValue

This needs a bit of design, before we start parsing the rest of language types.

using generated nodes from #3 and syntax kinds from #2 we need to be able to create parse rules for the following graphql types:

• #9
• #10
• #11
• #12
  • #13
  • parse OperationDefinition
  • #44
• #20
  • parse InlineFragment
  • parse FragmentDefinition
  • parse FragmentName
• #21
• #22
  • #23
  • #24
  • #25
  • #26
  • #27
  • #28
  • #29
  • #30
• #31
• #32
• #33
• #34
• #35
• #36
• #37
• #38
• #39
• #40
• #42
• #41
• #43
• #45
• #46
• #47
• #48
  • parse ScalarTypeDefinition
  • parse ScalarTypeExtension
• #49
• #50
• #51
• #52
  • #14
  • #15
  • #16
  • #17
  • #18
  • #19
  • #68
  • #68
• #53
  • parse InterfaceTypeDefinition
  • parse InterfaceTypeExtension
• #54
  • parse UnionTypeDefinition
  • parse UnionMemberTypes
  • parse UnionTypeExtension
• #55
  • parse EnumTypeDefinition
  • parse EnumValuesDefinition
  • parse EnumValueDefinition
  • parse EnumTypeExtension
• #56
  • parse ArgumentsDefinition
  • parse InputValueDefinition
  • parse InputObjectTypeDefinition
  • parse InputFieldsDefinition
  • parse InputObjectTypeExtension
• #57
  • parse Directives
  • parse Directive
  • parse DirectiveDefinition
  • parse DirectiveLocations
  • parse DirectiveLocation
  • parse ExecutableDirectiveLocation
  • parse TypeSystemDirectiveLocation
• parse whitespace and other ignored tokens #79
• #72
• #71
• #83

This needs a bit of design, as we should have a certain pattern that is very reproducible, as we have lots and lots of language types to create.

• parse FragmentSpread
• parse InlineFragment
• parse FragmentDefinition
• parse FragmentName

• parse ScalarTypeDefinition
• parse ScalarTypeExtension

Description

Tracking issue for the parser.

Requirements

Specified elsewhere.

Subtasks

• TODO

• parse string character
• parse block string character
• parse comment

The distinction can be done in the lexer. It can create two different tokens: StringValue and Comment.