graphql-api

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

Description
Remove any google fonts dependency from api-platform.

Example
Remove the google font stylesheet in line 8 of api-platform\core\src\Bridge\Symfony\Bundle\Resources\views\SwaggerUi\index.html.twig depending on a configuration variable?

Context
I'm working on an intranet application for a big company where any call to the fonts.googleapi.com CDN takes 30 seconds

Many user have expressed how useful GraphQL Voyager has been as they work on sites powered by WPGraphQL.

It would be nice to let users use GraphQL Voyager within their WordPress dashboard alongside GraphiQL.

See: https://github.com/APIs-guru/graphql-voyager

Please add arm64 release bin

When there are too many data-sources, the RPC call fails with "payload too large"

Affected subgraph

Error:

Payload is too big to load: Unexpected RPC error, error: Transport("Unexpected response status code: 413 Payload Too Large"), component: BlockStream

• [Source](https://github.com/pancakeswap/

Scope of updates:

• back end dependencies
• front end dependencies
• version of Go
• Node version
• versions of images in Dockerfiles
• dependencies in CI scripts

The fix for #509 enables using graphql interfaces and sub types in the client. However, it does so in a way that creates partial record accessors.

https://github.com/AlistairB/morpheus-repro/tree/partial-fields demonstrates the issue. stack build will produce the warning (it uses m

Add a GitHub action flow for publishing a new version (run build, run tests, publish to npm and GitHub packates) etc.

https://github.com/sisense/graphql2rest/actions/new

The Settings accepts several options which modify permalinks:

• Single endpoint path
• Persisted query base slug
• Other similar ones

We must validate that the input values are correct. Things to watch out for:

• Unsupported chars: !@#$%*()+='"...
• Too long: thispathistoolongthatthebaseslugcantprocessit
• Many instances of // together: /graphql-query/base//path/