so this playground bug that everyone seems to be ignoring is now affecting graphcool too (I guess you guys have upgraded): https://github.com/graphcool/graphql-playground/issues/312