GraphQL

Describe the bug
Using xframe ALLOW-FROM throws error in console: Invalid 'X-Frame-Options' header encountered when loading 'https://api.dev.mysite.com/uploads/my-file.pdf': 'ALLOW-FROM dev.mysite.com' is not a recognized directive. The header will be ignored.

https://strapi.io/documentation/v3.x/concepts/middlewares.html#response-middlewares
instructions for xframe indicate `ALLOW-FR

Is your feature request related to a problem? Please describe.
Mostly maintainability and code readability. When you make a change to any of these renderers you are forced to copy the same code more than three times

Describe the solution you'd like
A global component for rendering the response that receives as inputs:

• The response
• List of actions and a callback for each of the

Issue split from hasura/graphql-engine#6951

our pytest output has a pretty low signal:noise ratio, and it's often difficult to understand the cause of a test failure, if there is one. [Example: a 8600-line log for what turned out to be a flaky test that passed on a second run](https://app.circleci.com/pipelines/github/hasura/graphql-engine-mono/10008/workflows/5e17c7

Let's add a vite example for monaco-graphql? maybe even use vue or svelte instead of react?

https://github.com/vdesjs/vite-plugin-monaco-editor

• Editor button text should be Edit
• Edit and Preview buttons should stay highlighted (Primary color) based on current mode
• Need to add an interface option for Font type (same as other interfaces) for Sans, Serif, Mono. Should we have two? One for editor and one for preview? I think both should default to sans (like this GitHub editor).
• All WYSIWYG CSS should get copied from the

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.

Issue Type (check one)

• Bug Report

Description (type any text below) -->

When tabbing through the Spectrum interface it's difficult to know what you're interacting with since the outlines for tabbable elements have been removed.

If you force outlines back on you can see what is being tabbed.

*:focus {
    outline: 3px solid orange !important;
    outline-offse

cc @zackdotcomputer

Clerk has released a new v2 which is incompatible with v1:

• https://docs.clerk.dev/main-concepts/auth-v2
• https://github.com/clerkinc/clerk-sdk-node/releases/tag/v2.0.0

Because this is a breaking change, ideally it should be upgraded either before v1-rc or after v1 (included in v2). However, the core team maintainers most likely will not be able to prioritize this. S

Just gave VulcanJS a try after using Meteor for a while. I'm getting the following error:

`
Warning: React.createFactory() is deprecated and will be removed in a future major release. Consider using JSX or use React.createElement() directly instead.
meteor://💻app/packages/vulcan_lib.js:422
if (error) throw error; // eslint-disable-next-line no-console
^

[Error:

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.