Robert Mosolgo

Hi! Sorry for the trouble. Is `graphiql-rails` in your gemfile? Could you please share the line from your gemfile that includes it? you could try adding `require "graphiql-rails"` to the...

Sorry, I didn't add anything right away because I didn't want to be responsible for public user input 😅 I'll try to add one here when I get a chance,...

Yeah, I think you're right, although, I'm not really sure 😩 If you fork the gem and remove those hardcoded paths, then install your fork, does it work ok?

I'm not using it in production, but I think some folks are. The first parser in `graphql-ruby` was written in parslet which was about 100x slower than this one, but...

Oh, that makes sense, I'll keep testing in mind!

(This won't pass until a Rubygems version of `graphql` has Compatibility)

Sorry ... the `readme.md` is up-to-date for master, but I haven't released a gem version yet. You can either: - Install the master branch from GitHub with: ```ruby gem "graphql-libgraphqlparser",...

Cool, thanks for your response! If I get a chance to take a look, I'll be sure to report back :)

I got the answer to my question, and I don't have the bandwidth to work on a fix now (:'() so I figured I'd close it out. Feel free to...

Hey @JonRowe, sure thing, I just worked up a minimal reproduction here: https://github.com/rmosolgo/rspec-support/commit/8a32cffcf155f775821edee6de5529a9c7193907 Interestingly, I found that `subject(...)` was also required to replicate the problem -- if I moved that...