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

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

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/

This plugin might have been useful in the past as I forgot to uncomment some code, I guess it is worth adding it :)

https://github.com/sobolevn/flake8-eradicate

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

This is related to issue #552 . The previous PR solved most of the mismatches, but in the current snapshot (0.9.1+20-40e9f3a2-SNAPSHOT) arguments in root level operations still do not match.

Example

object Operations {
  @GQLDescription("query root")
  case class query_root(
      posts: PostsArgs => zio.UIO[List[Post]]
  )
}

case class Query_rootPostsArgs(
    ...
)

I