Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

semantic analysis: validate operation names in a document #148

Closed
lrlna opened this issue Jan 25, 2022 · 1 comment
Closed

semantic analysis: validate operation names in a document #148

lrlna opened this issue Jan 25, 2022 · 1 comment
Assignees
@lrlna
Labels
apollo-compiler issues/PRs pertaining to semantic analysis & validation

Comments

@lrlna
Copy link
Member

lrlna commented Jan 25, 2022 •
edited
Loading

Description

Validate the main document definition and add methods to the SourceDatabase.

Related Issues, #144, #147

Specification

  Documentation SEMANTIC PROCESSING ERROR WARNING HINT SUGGESTION QUERIES TO BE ADDED TO SOURCEDATABASE
Document Defined in spec   when multiple operation definitions are present, they must be named   call out to name operation definitions and point to where in the document they need to be named   operation_definitions → Vec<OperationDefinitions>
@lrlna lrlna mentioned this issue Jan 25, 2022
Closed
5 tasks
@lrlna lrlna self-assigned this Jan 25, 2022
@lrlna lrlna added the apollo-compiler issues/PRs pertaining to semantic analysis & validation label Jan 25, 2022
@lrlna lrlna changed the title Document semantic analysis: validate operation names in a document Jan 25, 2022
@lrlna
Copy link
Member Author

lrlna commented Jan 25, 2022

ooops this is part of #148 and doesn't need its own issue!

@lrlna lrlna closed this as completed Jan 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lrlna lrlna

Labels
apollo-compiler issues/PRs pertaining to semantic analysis & validation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@lrlna