Simplifies the graphile-build-pg inflector to trim the `ByFooIdAndBarId` from relations
Branch: master
Clone or download
Latest commit bc5e4f7 Jan 1, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.prettierrc.js Add prettier config Oct 12, 2018 v2 Jul 20, 2018 Update README Jan 1, 2019
index.js Simplify remote name if prefix matches Jan 1, 2019
package.json 4.0.0-alpha.0 Jan 1, 2019
schema.graphql Update README Jan 1, 2019
schema.simplified.graphql Update README Jan 1, 2019 More convenient command for testing Jan 1, 2019
test.sql Update README Jan 1, 2019
yarn.lock Track differences Jan 1, 2019


This plugin simplifies field names in the PostGraphile schema; e.g. allUsers becomes simply users, User.postsByAuthorId becomes simply User.posts, and Post.userByAuthorId becomes simply

Adding this plugin to your schema is almost certainly a breaking change, so do it before you ship anything! This is the primary reason this isn't enabled by default in PostGraphile.

This plugin is recommended for all PostGraphile users.


This plugin is implemented as a single JS file that does not need to be compiled at all - you can simply copy it into your project and customise it as you see fit.

Alternatively, you can write your own inflection plugin.


Given these tables:

create table companies (
  id serial primary key,
  name text not null
create table beverages (
  id serial primary key,
  company_id int not null references companies,
  distributor_id int references companies,
  name text not null
  • Query.allCompanies 👉 Query.companies (disable via pgSimplifyAllRows = false)
  • Query.allBeverages 👉 Query.beverages
  • Beverage.companyByCompanyId 👉
  • Beverage.companyByDistributorId 👉 Beverage.distributor
  • Company.beveragesByCompanyId 👉 Company.beverages (because the company_id column follows the [table_name]_id naming convention)
  • All update mutations now accept patch instead of companyPatch / beveragePatch (disable via pgSimplifyPatch = false)
  • If you are using pgSimpleCollections = "only" then you can set pgOmitListSuffix = true to omit the List suffix
  • Fields where the singular and plural are the same and a distinct plural is required are force-pluralised ("fishes") to avoid conflicts (e.g. singularize("fish") === pluralize("fish")).

Note: Company.beveragesByDistributorId will remain, because distributor_id does not follow the [table_name]_id naming convention, but you could rename this yourself with a smart comment:

comment on constraint "beverages_distributor_id_fkey" on "beverages" is
  E'@foreignFieldName distributedBeverages';

or with a custom inflector:

module.exports = makeAddInflectorsPlugin(
    getOppositeBaseName(baseName) {
      return (
          // These are the default opposites
          parent: "child",
          child: "parent",
          author: "authored",
          editor: "edited",
          reviewer: "reviewed",

          // 👇 Add/customise this line:
          distributor: "distributed",
        }[baseName] || null


yarn add @graphile-contrib/pg-simplify-inflector


npm install --save @graphile-contrib/pg-simplify-inflector



postgraphile --append-plugins @graphile-contrib/pg-simplify-inflector


const PgSimplifyInflectorPlugin = require("@graphile-contrib/pg-simplify-inflector");

// ...

  postgraphile(process.env.AUTH_DATABASE_URL, "app_public", {
    appendPlugins: [PgSimplifyInflectorPlugin],

    // Optional customisation
    graphileBuildOptions: {
       * Uncomment if you are using `simpleCollections: 'only'` and you never
       * want relay connections
      //pgOmitListSuffix: true,
       * Uncomment if you want 'userPatch' instead of 'patch' in update
       * mutations.
      //pgSimplifyPatch: false,
       * Uncomment if you want 'allUsers' instead of 'users' at root level.
      //pgSimplifyAllRows: false,
    // ... other settings ...

Naming your foreign key fields

By naming your foreign key along the lines of author_id or author_fk, e.g.:

  id serial primary key,
  author_id int not null references users,

We can automatically extract the field prefix: author and call the relation author rather than the default: user. This allows for a post to have an author, editor, reviewer, etc. all which point to users.

The reverse, however, is not so easy. On the User type, we can't call the reverse of all these different relations posts. The default inflector refers to these as postsByAuthorId, postsByEditorId, etc. However we'd rather use shorter names, so we introduce a new inflector: getOppositeBaseName. This inflector is passed a baseName (the part without the _id/_fk suffix, e.g. author, editor, reviewer above) and should return the opposite of that base name which will be prepended to the target type to produce, e.g. authoredPosts, editedPosts, reviewedPosts. Failing this, we just fall back to the default inflector; it will be up to you to add smart comments or a custom inflector to override these.

Handling field conflicts:

In most cases, the conflict errors will guide you on how to fix these issues using smart comments.