Juniper: Extract parser into its own crate

Created on 23 Feb 2017 · 7Comments · Source: graphql-rust/juniper

Hey there! I am interested in using the parser from this library in one of my own projects. Would it be possible to extract it into its own crate? Great work on this project, and hope to hear from you soon.

Ian

Source

ianks

👍2

Most helpful comment

This would be a nice improvement - not just for the use case of using the parser or type system outside of this project - it would probably cut down on compilation time for the test suite when working on isolated parts.

I imagine looking at the setup used by e.g. gluon would be useful; we probably would want the entire source code to still live in this repository and all released in lockstep with each other.

I'll see what I can do. Hopefully something that can be done before the 1.0 release.

mhallin on 26 Feb 2017

👍2

All 7 comments

I imagine looking at the setup used by e.g. gluon would be useful; we probably would want the entire source code to still live in this repository and all released in lockstep with each other.

I'll see what I can do. Hopefully something that can be done before the 1.0 release.

mhallin on 26 Feb 2017

👍2

Now that the repo is restructured, a good next step would be to extract the parser into it's own crate.

theduke on 19 Jul 2017

👍1

Just had a look at it. It seems the parser depends on the ast. So I guess that has to be moved into the parser.

pyros2097 on 28 Jul 2017

See also graphql-parser which uses pest.

naturallymitchell on 30 Aug 2017

By the way, is there any reasons why you didn't use a parser library such as combine (the one which I recommend) ? Is there any complexities with the grammar?