Summary

Where: https://www.gatsbyjs.org/docs/ssr-apis/#onRenderBody

What: Improve the example for onRenderBody or add another example, simple, that is not tied to a plugin.

Suggestion

// Object of props
const HtmlAttributes = {
  "data-whatever": "content"
}

// Magic
exports.onRenderBody = (
  { setHtmlAttributes }
) => {
   setHtmlAttributes(HtmlAttributes)
}

Describe the bug
Currently on iOS the app content is partially obscured by the bar at the bottom of the screen used for gesture based navigation (known as the ‘Home Bar’).

To Reproduce
Open the Postwoman PWA on a modern iOS device *without

hasura migrate reset

This command should clear the history of the migrations on the server and clear the local migrations. Basically, do steps 1 and 2 mentioned in this blog post: https://hasura.io/blog/resetting-hasura-migrations/

Issue Description

Since the old Instagram API will stop working on June 29 (See https://www.instagram.com/developer/), the url in https://github.com/parse-community/parse-server/blob/d0a9c709fea4cbdba540420353a36a0e89601ffb/src/Adapters/Auth/instagram.js#L9 needs to be changed to match the new "instagram_graph_user_profile" API. (See https://developers.facebook.com/docs/instagram-basic-disp

Describe the bug
I'm using java to develop a webservice and when I throw an exception it returns the correct response code, however the message does not contain spaces.

To Reproduce
Steps to reproduce the behavior:

1. throw exception that contains spaces in its messages in the app

Expected behavior
The returned message should contain spaces.

Screenshots
Insomnia:
![i

our beloved monaco-graphql could have a really nice test suite!

monaco-yaml's suite provides a fantastic example

we can just start with something similar to the hover/completion/diagnostics suites. we don't need to worry about multiple documents or completion with multiple schemas any time soon

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,

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

In the 1.15 update, the arrayItem property is introduced so we can get rid of the foo.$ field. I found this doesn't work for subschemas. I get the following error for a subschema defining an urlCollection arrayItem:

Error: "urlCollection" is Array type but the schema does not include a "urlCollection.$" definition for the array items"

It looks like it doesn't see the arrayItems field.

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.