It would be nice if the list of tables in the dropdown at /console/events/data/add was alphabetised. Here's what the current experience looks like:

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

Thanks for a really great utility, just discovered it today!

Expected Behavior

It would be nice if it was possible to look at the results of a subscription while having it stopped, especially for faster updating subscriptions. I known you can turn off autoscroll but if you want to save the results you still have to manually cut and paste, unlike query results where you can use the download

In the graphql_map_input_fields_to_wp_query filter, the $post_type is the last parameter. This is inconsistent with the other graphql_map_input_fields_* filters. For example in graphql_map_input_fields_to_get_terms the $taxonomy parameter is the third parameter (while the $context & $info parameters are the last two in all of the graphql_map_input_fields_* filters). For consistency sake, i

What would you like to be added:

Currently config uses one file per environment (eg. dev, staging, prod, etc) we should move to a multi-file config where we have one folder per environment and config values can be split across multiple files within this folder.

Why is this needed:

For setups where there are

• Are you running a release or master: master
• Issue is about a fresh instance (no data in db) or restart: fresh

This seems a known/unfinished issue based on the commented 'Name' field in the code noted below, but I was hoping it could be addressed as it would greatly ease the discovery of the graphql endpoints generated by the db tables as they would become available in GraphiQL in #13

``

The documentation home page today is just the Getting Started page. We could create a docusaurus landing page so we can have a more visual appealing site to view and that is SEO friendly.

See: https://docusaurus.io/

I found a place where I had this:

from .enums import ExampleEnum

ABC = strawberry.type(ExampleEnum)

I think we should add a safety check as we already for enums: https://github.com/strawberry-graphql/strawberry/blob/master/strawberry/enum.py#L24-L25

We should only allow to decorate classes with strawberry.type, strawberry.input and strawberry.interface

If a user writes a subgraph referencing contract addresses from (for example) a testnet, and then accidentally deploys the subgraph to a graph node running mainnet, the subgraph will run but won't find any events. We can provide a better experience using eth_getTransactionCount to check that the contract addresses exist on

sttp 3.0.0 has been released for a while now. https://github.com/softwaremill/sttp/releases/tag/v3.0.0