initial commit

Author: Tim M

.gitignore

@@ -0,0 +1 @@
+node_modules

.prettierrc

@@ -0,0 +1,3 @@
+{
+  "semi": true
+}

README.md

@@ -0,0 +1,44 @@
+# postgraphile-plugin-many-create-update-delete
+
+<!-- ![npm](https://img.shields.io/npm/v/postgraphile-plugin-many-create-update-delete) -->
+[![PRs Welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg?style=flat-square)](http://makeapullrequest.com)
+
+This plugin implements mutations that allow many creates, updates, and deletes in a single transaction.
+
+## Getting Started
+
+View the [postgraphile docs](https://www.graphile.org/postgraphile/extending/#loading-additional-plugins) for information about loading the plugin via the CLI or as a NodeJS library.
+
+## Plugin Options
+
+This plugin respects the default option to disable mutations all together via ```graphileBuildOptions```.
+
+```js
+postgraphile(pgConfig, schema, {
+  graphileBuildOptions: {
+    pgDisableDefaultMutations: true
+  }
+});
+```
+
+## Smart Comments
+
+You must use smart comments to enable the many create, update, and delete mutations for a table, since they are not enabled by default to prevent crowding with the other autogenerated postgraphile default mutations. The single tag ```@mncud``` is all that's needed.
+
+```sql
+comment on table public."Test" is
+  E'@mncud The test table is just for showing this example with comments.';
+```
+
+## Usage
+
+The plugin creates new mutations that allow you to batch create, update, and delete items from a given table. It works with primary keys for updates and deletes using the input patch that postgraphile generates. All creates, updates, and deletes have scoped names with "mn" in front of the mutation name to prevent conflicts with other mutations.
+
+### Creates
+```mnCreateTest``` would be an example mutation name, and we'll say it has attributes of test1 (a boolean), and name (a varchar). You'll see the required input has the clientMutationId and also a field called ```mnTest```, where ```mnTest``` will take an array of items that use the table input type. Since it uses the table input type, the required items are all listed as expected.
+
+### Updates
+```mnUpdateTestByName``` would be the update example name, assuming the name is the primary key. Updates have a required input with the clientMutatationId and a patch. The patch field accepts an array of table patch items. You ***MUST*** provide the primary key within the patch items b/c that is what's used in the where clause to update the correct row.
+
+### Deletes
+```mnDeleteTestByName``` would be the delete example name. Deletes have a required input with the clientMutationId and a patch. The patch field accepts an array of table patch items, but only the primary key items are used. You ***MUST*** provide the primary key within the patch items b/c that is what's used in the where clause to update the correct row.

build/PostGraphileManyCreatePlugin.d.ts

@@ -0,0 +1,4 @@
+import * as T from './pluginTypes';
+declare const PostGraphileManyCreatePlugin: T.Plugin;
+export default PostGraphileManyCreatePlugin;
+//# sourceMappingURL=PostGraphileManyCreatePlugin.d.ts.map