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.

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

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

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

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

npm run build since babel-node isn't meant for production use. My attempt is failing:

$ GLOBIGNORE="node_modules/*"; babel **/*.js -o build.js 
ReferenceError: [BABEL] data/chapters.js: Unknown option: /Users/me/gh/api-model/node_modules/babel-preset-env/lib/index.js.__esModule. Check out http://babeljs.io/docs/usage/options/ for more info
    at Logger.error (/usr/local/lib/node_mod

https://github.com/gramps-graphql/gramps-express/blob/915a34d1816f403b707b4fc562d237554428d49e/src/helpers/GraphQLConnector.js#L98

This should point to the GrAMPS docs or be removed altogether since there aren't specific docs available for this error right now.

Hi All,

I've asked the question on SO, basically I'd like to have an example of a LIKE query : which silently gives no results (does not throw any error and doesn't answer correctly) knowing that in mongoose, filter: { name: "/MICH/i" } will return results where name is LIKE "mich" in a case