meta: docs issue tracker

[saihaj]

Track all docs related issues for GraphQL.JS open in graphql/graphql-js, graphql/graphql.github.io.

• parameterized query variable values aren't passed to parseLiteral of GraphQLScalarTypes #433
• Improve Lackluster Documentation #1368
• Document subscription support #2098
• Pass previous object to resolvers #2206
• Links Broken on APIReference-GraphQL Markdown #2244
• Documentation of GraphQLScalarType is outdated #2567
• Update Tutorial-ObjectTypes.md #2892
• Add documentation for the executeSync method #2941
• Requesting multiple examples for in-browser usage #2950
• Easier navigation to graphql-js tutorial graphql.github.io#119
• graphql.js custom scalar type docs are very vague graphql.github.io#163
• graphql-js docs don't list any class methods graphql.github.io#252
• Update APIReference-TypeSystem.md graphql.github.io#683
• Rework examples to avoid using buildSchema graphql.github.io#669
• Docs :: GraphQLResult is not defined graphql.github.io#1049
• Update APIReference-TypeSystem.md graphql.github.io#1051
• [2020-09-16] Write a contribution guide graphql-js-wg#3
• Security bug reports graphql-js-wg#42
• Upgrade Guides #3366
• fix: Corrected a Typo graphql.github.io#1163
• Add docs for language types Parser:Document & Visitor:AST_node #3868

[saihaj]

Started the site here #3269

[kasir-barati]

Hi @saihaj, Just wondering if we could use ES6 syntax at least if we ain't aiming for TS. I am talking about examples that we have here: https://graphql-js.vercel.app/tutorials/running-an-express-graphql-server

I just think that this much work is being poured into this. So let's do a modernization too, like what is going on here: graphql/graphql.github.io#1821

Any comment?

Just realized that I was seeing an outdated version of doc: https://graphql-js-git-16xx-the-graph-ql-foundation.vercel.app/