https://www.apollographql.com/docs/apollo-server/data/errors/#codes

Mentions that:

In addition to stacktraces, Apollo Server's exported errors specify a human-readable string in the code field of extensions that enables the client to perform corrective actions. In addition to improving the client experience, the code field allows the server to categorize errors. For example, an Authenticat

Since typescript-generic-sdk got merged, we need to add docs, usage and examples.

Related: dotansimha/graphql-code-generator#2978

Update

The website is now live under a new domain 🎉

https://typegraphql.com/

This is the last domain change I hope 😄

Background

The typegraphql.ml domain from Freenom has expired (or cancelled because I had no reminder on email as usual!), so the docs site is not reachable by this URL.

Freenom has marked typegraphql.m

https://github.com/prisma/nexus/search?q=subscription&unscoped_q=subscription I see they are in Nexus, but I can't find any mention of them on https://nexus.js.org/docs

We just need a piece of documentation because there is literally no documentation about directive locations except from the spec. The spec is not easy to read. Something like this would make sense

directive @field_definition on FIELD_DEFINITION
directive @argument_definition on ARGUMENT_DEFINITION
directive @object on OBJECT
directive @interface on INTERFACE

interface Foo @inter

Directive declaration definition:
graphql/graphql-js#318

To do:

• add directive to Type Definitions
• add a Directive Types section with a declaration and usage examples
• add a directive declaration (one liner) in the What does it look like? example

Maybe we could get rid of the Input with default value and Input with multiple arguments ex

SyntaxError: Error while loading rule 'graphql/template-strings': Unexpected token  in JSON at position 0
Occurred while linting /Users/devalias/dev/REDACTED/schema.graphql
    at JSON.parse (<anonymous>)
    at Object.readSchema (/Users/devalias/dev/REDACTED/node_modules/graphql-config/lib/utils.js:141:38)
    at GraphQLProjectConfig.getSchema (/Users/devalias/dev/REDACTED/node_modules/g

I am confused as to how an example such as this, found in your documentation, is compatible with graphql-auth-directives:

const server = new ApolloServer({
  schema: augmentedSchema,
  context: ({ req }) => {
    return {  /* Note: We return a context object containing both `driver` and `req` fields */
      driver,
      req
    };
  }
});

Given that `graphql-auth-directiv

I think it would be super useful if one could include headers when defining the endpoints.

Something like:

endpoints: [{
  namespace: 'model',
  typePrefix: 'Model',
  url: 'http://localhost:8080/graphql' // url to a GraphQL endpoint,
  headers: {
    'Authorization': 'Bearer **********************',
    'content-type': 'application/json'
  }
}

https://github.com

• If TypeScript is so great, how come all notable ReactJS projects use Babel?
• TypeScript-Babel-Starter
• typescript-vs-flowtype
• [utility-types](https://github.com/piotrw

Annotation @GraphQLDescription( value ="${message}") not read from Properties files