The search functionality in the Data & Schema Management of Hasura seems to filter records considering the case of letters as well.
If this was an intended functionality, it's still better to show the tables which match the filter condition and don't match the letter-case below the tables that match with the exact letter-case.

Experience Report

I am currently ingesting a large continuous streaming data set. The most recent data is the most important data. The oldest - either by policy or by least importance needs to be aged-off. Today, we use Neo4J Community Edition. We perform a query to find nodes/relationships older than a specific date and then delete them.

Note: Feature requests are judged based on user

https://www.apollographql.com/docs/apollo-server/data/errors/#codes

Mentions that:

In addition to stacktraces, Apollo Server's exported errors specify a human-readable string in the code field of extensions that enables the client to perform corrective actions. In addition to improving the client experience, the code field allows the server to categorize errors. For example, an Authenticat

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

Duplicated server using code from https://github.com/prisma/graphql-yoga#mocking and got the following error:

Error: No schema defined

server start code snippet:

...
const server = new GraphQLServer({ typeDefs, mocks })

const options = {
	endpoint: '/',
	playground: '/playground',
	subscriptions: '/',
	logFunction: (e) => console.log,
	debug: true,
}
server.start(options, 

I'm sure there are a lot of people, myself included, excited to use Rejoiner, but are rusty with their Java tooling knowledge.

Would love to see a very easy copy/paste how-to to get rejoiner up and running with vanilla Java. A quick start guide would help immensely.

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.

We just need a piece of documentation because there is literally no documentation about directive locations except from the spec. The spec is not easy to read. Something like this would make sense

directive @field_definition on FIELD_DEFINITION
directive @argument_definition on ARGUMENT_DEFINITION
directive @object on OBJECT
directive @interface on INTERFACE

interface Foo @inter

https://github.com/daptin/daptin/blob/aa77b35feeb48557b42a13b7a05fb291eb1e562a/docs_markdown/docs/features/enable-data-auditing.md#L1

This issue was generated by todo based on a todo comment in aa77b35feeb48557b42a13b7a05fb291eb1e562a. It's been assigned to @artpar because they committed the code.

Hi, I'm reading the docs about resolvers (https://ariadnegraphql.org/docs/resolvers) and got stuck in the explanation of def resolve_username(obj, _*). As explained in the docs, obj is a value returned by a parent resolver. In this case, the parent of the username field would be the User type, but this type does not have first_name or last_name. Or am I missing something? Could the ex

What would you like to be added:

Document what it would take to get Super Graph working with Yugabyte DB a distributed database that is designed to be compatible with Postgres. Super Graph makes use of a bunch of Postgres specific features like querying for database tables and columns, lateral joins, json functions et

We should add some links to Prisma examples in the README & docs.

I recently came across two use cases that would both be solved by a central document to give space for explanations and background information for decisions.

1. In-line comments

For a boilerplate, in-line comments are a bit annoying. They should be kept out of code, such as here:

const db = new Prisma({
  typeDefs: 'src/generated/prisma.graphql', // the auto-generated GraphQL sch

First, just wanted to mention thanks for creating this library, it's awesome and working well for me so far. However, I think the documentation of all the supported options could be improved. For example, I had no idea the annotation @GraphQLEnvironment existed until I looked through the other issues in GitHub. It seems like there is a ton of configuration potential, so it would be helpful to

perhaps a little confusing about why src and queries are sibling directories, as src also contains some .graphql too

Thanks @rarkins for this feedback. Would be great to hear other suggestions.

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/

Developing on the default config with localhost:3000 is fine.

However when I tried to test the local dev version from a device in the local network, say 192.169.110.1:3000, one of the client requests is still pointing to localhost:3000. Specifically, it's http://localhost:3000/__meteor__/dynamic-import/fetch, which makes the app unresponsive/unable to login from devices other than localhost.

I am confused as to how an example such as this, found in your documentation, is compatible with graphql-auth-directives:

const server = new ApolloServer({
  schema: augmentedSchema,
  context: ({ req }) => {
    return {  /* Note: We return a context object containing both `driver` and `req` fields */
      driver,
      req
    };
  }
});

Given that `graphql-auth-directiv

With the following schema:

schema {
  query: Queries
}

type Post {
  similar(limit: Int!, offset: Int): [Post!]!
}

type Queries {
  users: [User!]!
  posts: [Post!]!
}

type User {
  similar(limit: Int!): [User!]!
}

SchemaWriter will generate 2 case classes named SimilarArgs that clash with each other.

They should be converted to ID :)

import uuid

@strawberry.type
class X:
    id: uuid.UUID

if I add one or more fields to my mongoose model, it would great to update the generated GraphQL files