❯ hasura console --envfile /etc/cuddlefish-dev.env
FATA[0001] loading .env file failed: open /Users/skainswo/dev/cuddlefish/hasura/etc/cuddlefish-dev.env: no such file or directory

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

Description
To be able to optionaly remove the google fonts dependency on any page of the api-platform.

Example
Remove the google font stylesheet in line 8 in the file 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 100000+ employees company and

Currently, in order to register a field to an Edge you have to know the full Edge name, like RootQueryToPostConnectionEdge and that's cumbersome.

It would be nice to have something like: register_graphql_edge_field( $fromType, $toType, $fieldName, $config );

I think it's easier to know the from/to type than know the fully qualified edge name.

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

Describe the solution you'd like
I'd like to use this project with Ktor but the documentation seems to be lacking for any framework other than Spring. I believe it would be nice to improve the documentation with some other Kotlin frameworks taken into account, Ktor being one of them. At least some getting started docs would be perfect.

It would be nice to see aiohttp integration with your library.

Another day, another weird GraphQL schema!

I'm working with an e-commerce platform called commercetools. They have a graphql schema that looks like this:
https://github.com/commercetools/sunrise-spa/blob/master/graphql.schema.json (They are not even using this type ...).

They decided to define EnumValue and this clashes with the import: import caliban.client.Value._.

I think this is

We have types in various places that do not follow the Rust naming conventions. A good example are all the GraphQL* types that should be spelled GraphQl* to follow the conventions.

It would be nice to clean this up by renaming all types that don't follow the rules.

Marking this as a "good first issue", as it's low-hanging fruit and would be a good way for new contributors to contribute somet