Summary

Our docs relating to GraphQL sometimes have CodeSandbox samples where viewers can edit their query. However, these pages are represented in the markdown as raw iframes and are quite ugly:

<iframe title="A basic query" src="https://7118

Describe the bug
Find-one endpoint /resource/:id responses with 500 status code instead of 404, this happens with MongoDB setup.

Steps to reproduce the behavior

1. Setup Strapi with MongoDB configuration.
2. Create a collection (resource).
3. Give findOne access to the public.
4. Send a request to /resource-name/any-invalid-id.

Expected behavior
404 response.

**Sys

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

The search functionality in the Data & Schema Management of Hasura seems to filter records considering the case of letters as well.
If this was an intended functionality, it's still better to show the tables which match the filter condition and don't match the letter-case below the tables that match with the exact letter-case.

Is your feature request related to a problem? Please describe.
Deployed Parse server using k8 and used /parse/health for the readinessProbe and livenessProbe probe. But when deploy new code and broke the database connection, /parse/health still returns 200 OK. So old container was killed and new broken one brought online

Describe the solution you'd like
Only return 200 ok after db is

Describe the bug
Any attempt to test a subscription directly to the Prisma server via Playground returns the following error:

The provided query doesn't include any known model name. Please check for the latest subscriptions API.

In review of the WS transactions in the browser console, I can see I am receiving this response from the Prisma endpoint, but nothing is being logged by Pri

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

Is your feature request related to a problem? Please describe.
An external API does not always respond successfully. Server errors for example 50x or 429 Too Many Requests may occur. Manually pressing the send button while waiting for a successful response can be tedious.

Describe the solution you'd like
Be able to set the number of retries and the expected/unexpected status codes o

Currently, if look at the windows_e2e tests on circle under the write e2e files step, you will see this warning:

Error autodetecting timing type, falling back to weighting by name. Autodetect no matching filename or classname.  If file names are used, double check paths for absolute vs relative.
Example input file: "e2e\\api\\add-many.e2e.1.ts"
Example file from timings: "C:\\Users\\****

Prerequisites

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

Issue Description

The description field is missing in the input schema when you are creating a shop. It's defined in the graphql schema but not in the validation schema. So, if you create a shop with description,

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

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

Pluralize has unexpected results, it can't be used safely in code. It is only relevant for UI features.
Example: latin words, "schema" => "schemata", "datum => data", plural word are kept plural etc.

Adding an "s" blindly is more efficient though semantically incorrect sometimes. Better, allowing user to provide it's own names for resolver.

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

It would be great to add regex capabilities to redirects like so:

redirects: {
  "/folder/:slug(regexhere)": {
    "location": "https

Following the tutorial, ends in a not working state.

The problem arises when using the command "prisma deploy" for the first time.

https://www.howtographql.com/react-apollo/1-getting-started/

https://github.com/howtographql/howtographql/blob/master/content/frontend/react-apollo/1-getting-started.md

Section: Backend
Subsection: Deploying the Prisma database service

The commands

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.