should not be new validateSchema called in runQuery?

[jardakotesovec]

• has-reproduction
• feature
• docs
• blocking
• good first issue

in graphql-js 0.12 schema validation was taken out from constructor and moved to validateSchema. Therefore it's used explicitly in wrapping function from 0.12.0. Did not find that runQuery would be adjusted for this change, so its now basically skipping this validationSchema step. Is that intention or oversight?

[abernix]

Thanks for reporting this originally and sorry it's taken so long to triage this.

I'll close this since most of the request pipeline has been overhauled in Apollo Server as #1795 and we haven't seen any recurring reports of this, but if you're still experiencing problems with this, please do open a new issue with a runnable reproduction (per the instructions when opening a new issue).

Thanks!