Description

Migrate some dependencies in devDependencies for gatsby package.

At least these (non exhaustive):

• "@typescript-eslint/eslint-plugin"
• "@typescript-eslint/parser"
• "eslint"
• "eslint-config-react-app"
• "eslint-loader"
• "eslint-plugin-flowtype"
• "eslint-plugin-graphql"
• "eslint-plugin-import"
• "eslint-plugin-jsx-a11y"
• "eslint-plugin-react"
• "eslint-plugin-

• 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 subm

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

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

Is your feature request related to a problem? Please describe.
There is no comprehensive tooling while working with MQTT brokers.

Describe the solution you'd like
A simple interface to connect to an MQTT broker.
Subscribe to topics
Publish to topics

Describe alternatives you've considered
MQTT Lens

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

We need to add tests for the /explain API.

Note: will add docs link here once this is done: hasura/graphql-engine#870.

• Doc page: tutorial-5/index.md
• Doc version: release/v1.2.0

The image immediately following the text below has arrows going opposite the way the sentence describes them.

A mentioned edge points from a Tweet node to a User node. These users are the ones who are mentioned in the tweet.

![image](https://user-images.githubusercontent.com/487774/734

Is your feature request related to a problem? Please describe.
The GraphQL documentation portion of Insomnia does not resolve Union data types. Drilling into one of these types always produces a no description value to be displayed.

Describe the solution you'd like
It would be great if when selecting a Union data type, any types that make up that union are presented in the same

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

https://leapgraph.com/graphql-api-security

This article mentions several add-on packages that Reaction may want to use. This issue is simply to investigate whether these vulnerabilities are present and try adding the packages to solve them.

If I do this, I get 404 on the first 2 routes:

import MeetupCreation from '../components/MeetupCreation';
import MeetupList from '../components/MeetupList'
import MeetupAdminList from '../components/MeetupAdminList'

addRoute({ path: '/create', component: MeetupCreation })
addRoute({ path: '/list', component: MeetupList })
addRoute({ path: '/admin/list', component: MeetupAdminList })

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