Documentation issues

[yaacovCR]

Opening this issue to collect issues related to documentation, as well as to open discussion of method of documentation, via typedoc a la fork, via Gatsby as in upstream, or other.

• Add docs for full api including types, closes Lack of documentation on TS types/interfaces #1219, mergeSchemas onTypeConflict still mentioned in docs, but no longer exists #1133
• Remove all launchpad mentions, closes URL not found #1292, Remove launchpad examples from docs #1151, Migrate examples away from Launchpad #1129, launchpad example has a bad url for remote schema #1097
• Remove all githunt mentions, closes Invalid links in docs #1259, Links to GitHuntAPI Are Broken On the page #1223, The links in the connectors documentation are broken #1187, Not working links and missing repo: GitHunt #1182
• Update schema directive docs to note that rename-directive-package is an example, not existing package, closes rename-directive-package #1287
• Update documentation about status of info.mergeInfo.delegateToSchema, which is identical to exported delegateToSchema itself, closes Improve documentation on mergeInfo.delegate #453
• Ideally, automatically ensure all examples compile. Alternatively, just fix typos, closing Remote schema, node-fetch example, unexpeced colon #1127
• Create new stitching examples, including stitching to relay-style subschemas with their own node fields, batching, passing authentication data, closing Thoughts on merging schemas that have their own Relay node lookups #1013, Batching requests to stitched schemas #884, Stitching secure subscriptions using makeRemoteExecutableSchema #864 .
• requireResolversForArgs and other resolverValidationOptions documentation says options will cause schema generation to throw an error when enabled, but no error is thrown -- a warning is printed to the console. It would be a breaking change to throw an error, but this should be better documented, with possibly a new flag considered to add the desired functionality if there is truly a need. Fixing the documentation addresses requireResolversForArgs doesn't throw an error if resolver is missing #1315, resolverValidationOptions do not throw an error #1196.
• remove references to deprecated apollo-fetch, closes Schema stitching does not work with apollo server 2.0 #972, TypeScript Compile Type Error while calling introspectSchema with 'apollo-fetch' #748
• consider replacing node-fetch in examples with cross-fetch as node-fetch has types issues, closes Type collision from node-fetch #877

[peterlau]

The documentation references the new stitchSchemas API https://www.graphql-tools.com/docs/schema-stitching which is not available in the stable 5.0.0. build.

Seems to me that the canonical documentation site should be pinned to the latest stable build and not describe an unreleased feature.

[yaacovCR]

You are absolutely correct, apologies for the oversight.

You should be able to get almost all the stitchSchemas goodness out of mergeSchemas in v5.

[yaacovCR]

can track docs improvements in #1337, no need for separate pinned issue.