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

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

The documentation for Importing NDF format data does not mention that the method will not be supported in future as per the message in the 'prisma import' command...

"Warning: The prisma import command will not be further developed in the future. Please use the native import features of your database for these workflows. "

https://www.prisma.io/docs/prisma-cli-and-configuration/data-import

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

2D geometries are supported. How about 3d geometries? ST_3DDWithin etc

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

Hey this is a really cool app that I guess a lot of people (incl me) would learn from.

Would be nice if there is some slightly more detailed documentation on how to forge this app.

Cheers

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

• Insomnia Version: 7.0.5
• Operating System: Ubuntu 18.04

Details

I noticed that the GraphQL editor has an awesome deprecation-warning built-in, but the deprecation warning is not shown in the schema explorer. I think that would be a nice edition - preferably with a big fat warning icon :)

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

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

We should use https://github.com/jonschlinkert/parse-github-url to intelli

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 })

Prerequisites

• I am running the latest version. (up upgrade)
• I searched to see if the issue already exists.
• I inspected the verbose debug output with the -v, --verbose flag.
• Are you an Up Pro subscriber?

Description

Currently the TLS version defaults to 1.0. I have to manually upgrade it to 1.2. So it would be nice if it could be specifed in the custom

What I'm trying to achieve

Create checkout with a checkout line.

Steps to reproduce the problem

1. checkout = Checkout.objects.create(...)
2. checkout.lines.create(...) or CheckoutLine.objects.create(checkout=checkout, ...)

OR

1. checkout = Checkout.objects.create(...)
2. if checkout: pass

What I expected to happen

Database insertion without additional coun

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

Link is not correct in https://www.howtographql.com/graphql-java/2-queries/

To add GraphiQL, copy the example index.html from GraphiQL’s GitHub repo

Just try to open it - https://github.com/graphql/graphiql/blob/master/example/index.html
It doesn't work.
Seems like correct one is - https://github.com/howtographql/graphql-java/blob/master/src/main/webapp/index.html

And it's not neede

Hello,

First of all, thank you to everyone involved in writing this package! I have used it extensively and started publishing some helpers at https://github.com/Fanatics/graphql-ast-helpers

One thing I'm confused about - calling printer.Print doesn't seem to emit the descriptions in the standard triple-

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