Summary

Currently the docs recommend to set absolute imports within webpack. While this does work it only applies to webpack. If you are trying to eject from gatsby's eslint rules or use other tools they will not know how to resolve these and will complain. For those using yarn 1 or 2 there is a better way

• I have created my request on the Product Board before I submitted this issue
• I have looked at all the other requests on the Product Board before I submitted this issue

The functionality of the bootstrap.js file is great, however, I think its opposite is missing. Many times we need to teardown connections and gracefully announce that we are tearing down the server. This wa

Too wide (and falsy) segregation of GraphQL Types and Resolvers

The first example of this is new ObjectType in src/data/queries/index.js importing fields.
Fields should be taken in context of parent type, not as standalone information.

This can ensure some users that custom types cannot have own field resolvers which is false.

In fact, much of fields which can have own resolvers

It would be great if we could create dynamic headers.

for example, some APIs may use a nonce and then based on the nonce we would need to create the hash and also update headers with that hash.

I want use webrtc with parse server, can i send sdp and ice data to peer user (without save) using parse ?

Describe the bug
When the elevated database user account does not have permission to create a schema, it cannot establish a connection with an existing database.

But when I provided the root account, I successfully established a connection with the database, but prisma created a schema called prisma.
Look like this:
![image](https://user-images.githubusercontent.com/18180417/57507662-fc

Feature requests

Based on the documentation at https://graphql.org/learn/execution/#root-fields-resolvers, I expected that resolvers would always receive the parent/previous object as the first argument. However when I tested the library, the arguments received by the resolvers are actually (args, context, info).

This doesn't match the documentation, and is a serious limitation when one

I think the client-side URL routing on your docs website is broken?

Reproduction:

1. Go to https://www.apollographql.com/docs/react/
2. In left hand menu click "Api Reference" then "class ApolloClient"
3. client-side JS pushes the URL "https://www.apollographql.com/docs/react/api/apollo-client/"
4. reload page
5. get a page not found error

I think the URL should be something like: "http

The grafana board seems to be outdated, a lot of the panels have no data, it seems to be missing in /debug/prometheus_metrics...

What version of Dgraph are you using?

v1.2.1

Have you tried reproducing the issue with the latest release?

Yes

What is the hardware spec (RAM, OS)?

Kubernetes 3 x 16gb 4cores, prometheus and grafana running locally.

Steps to reproduce the iss

Describe the bug
Calling a route which returns a 301 response correctly redirects. If the route then no longer returns a 301 insomnia still will redirect to the resource. I cannot find any other way then completely wipe out all insomnia configuration to reset this cached redirect.

To Reproduce
Steps to reproduce the behavior:

1. call a route which returns 301
2. let the route no lon

Description

Bit does not generate docs for React TS components.

for example:

https://bit.dev/eden/react-ts-demo

Specifications

• Bit version: 14.7.4
• Node version: 10.15.3
• npm / yarn version: 6.4.1 / 1.16.0
• Platform: macOS
• Bit compiler (include version): bit.envs/compilers/react-typescript@3.1.44
• Bit tester (include version):

Context and additional inf

I had some issue with how async throw() assertions work or some such that caused me to skip this. would be great to:

• convert codemirrror-graphql unit tests from mocha and chai to jest and jest.Assert. rename to follow jest spec.js pattern
• ensure all tests do not use chai across the monorepo
• remove mocha/chai from the build process

Prerequisites

• Are you running the latest version?
• Are you able to consistently reproduce the issue?
• Did you search the issue queue for existing issue? Search issues

Issue Description

The Surcharge schema (SimpleSchema) in surcharges plugin doesn't have all fields. This is because we're running the validation

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

Why not providing a mongo/mongoose code example in the examples folder, as this seens to be a very common usage scenario?

• Add option to enable analyze on queries only
• Add option to export as JSON rather than text (for import into https://tatiyants.com/pev/#/plans/new)
• Add button (or similar) to easily copy the SQL query or explain results

It returns an object like {0: 'firstValue'}, try with apolloServer.corsWhitelist for example, instead of an array. Accessing through Meteor.settings does work though.

Maybe it happens only for values that are nested within an object.

What would be the minimal IAM Policy for deploying, I know the policy on the website, but that has also access to EC2 and is quite broad. For example I would not need to control a domain from there.

Like it would be a role that you could put on Travis-CI and not worry about them deleting your EC2 instances.

I tried deleting everything other than Lambda, API Gateway and S3, but then I began

What I'm trying to achieve

To experiment with saleor

Steps to reproduce the problem

1.Fork saleor
2. Press the button in the readme section of saleor (of my fork) which redirects you to heroku deployment
3. Deploy saleor

What I expected to happen

Bad Request (400)

Hello!
I wrote a Notification service for my application, and use a subscription to a new notification for the user, according to the selected topics.

After changing the topics for the user, it is logical to resubscribe to notifications with new parameters, but nowhere in the documentation for useSubscription hook there is no mention or example for such a common scenario.

I ask you to help

I've recently started to implement a graphql server in golang, and It was a good experience.
I read about libraries for creating graphql server in golang and these options came across:

• https://github.com/graphql-go/graphql
• https://github.com/99designs/gqlgen
• https://github.com/graph-gophers/graphql-go

graphql-go/graphql is the first library that started implementing graphql in g

Let's say each comment around field and definitions is an entity. Is it possible to group those entities in some logical sections?

e.g. group documentation regarding Credentials in 1 sections and other data in another. So they are all not generated always in Queries/Mutations, but

-> Queries -> Credentials section
-> Mutation -> Credentials section

or

-> Credentials:
- Queries

Summary

Add a site AMP version.

Basic example

Nuxt.js has an example: https://github.com/nuxt/nuxt.js/tree/dev/examples/with-amp
Gatsby AMP Plugin: https://www.gatsbyjs.org/packages/gatsby-plugin-amp/

Motivation

The AMP Project support is very important to accessibility and Google's Pagerank. So, it could will be awesome had this support in Gridsome.