Jay Herron

@alexsteinerde I took a look at your forks - thanks for referencing them! I'm agree that we should probably not require `GraphQL` changes in order to support the Graphiti feature...

Hey guys, sorry I'm kinda late to this party. I forgot this MR existed and made [a new MR](https://github.com/GraphQLSwift/GraphQL/pull/128) adding this functionality using the GraphQL `Map` object like d-exclaimation suggested....

Resolved by https://github.com/GraphQLSwift/GraphQL/pull/124

@dfperry5 Yeah, SDL support is still an outstanding area for improvement.

@dfperry5 That would be awesome! I'm actually not too familiar with where SDL stuff lives in graphql-js. I believe it is built into the [lanugage parser](https://github.com/graphql/graphql-js/blob/main/src/language/parser.ts), and that our repo...

Yeah, it looks very cool! Thanks for sharing @rex-remind101! I had a few questions as I reviewed: - If I'm reading right, it looks like it does two things: Converts...

Cool, thanks for your take on those questions. Overall, I'm on board with bringing this package into the GraphQLSwift org. However, I'd hesitate to replace the [GraphQL parser](https://github.com/GraphQLSwift/GraphQL/blob/main/Sources/GraphQL/Language/Parser.swift) with this...

> Since this issue is related to SDL support, I wonder what's missing from the existing parser to support it? I think the GraphQL Parser already supports SDL. Check out...

I'm marking this as resolved, since `async`/`await` support was added by https://github.com/GraphQLSwift/Graphiti/pull/78

I've left it open for the moment because it includes more than just `async`/`await` additions. For example, the later commits explore adding custom directive support to this package.