@nextlyhq/plugin-form-builder 0.0.2-alpha.70 → 0.0.2-alpha.72

package/README.md

@@ -39,10 +39,16 @@ const fb = formBuilder({
 
 export default defineConfig({
   plugins: [fb.plugin],
-  collections: [...fb.collections],
+  collections: [
+    /* your own collections only */
+  ],
 });
 ```
 
+The plugin registers its `forms` and `form-submissions` collections itself. Don't
+also add `fb.collections` to `collections`: the same slug twice stops the app
+from booting with a duplicate `forms` collection.
+
 > A `formBuilderPlugin` default-instance shortcut is also exported for cases where no customization is needed. See [the plugin docs](https://nextlyhq.com/docs/plugins/form-builder) for the full options reference.
 
 ## Admin components

package/dist/index.js

@@ -69,9 +69,9 @@ function applyRedirectPattern(pattern, document) {
 * the role screen grants it: `read-form-submissions` to read submissions,
 * `update-forms` to edit a form.
 *
-* A collection's rule is the whole answer for a signed-in user, so "signed in"
-* here would admit every staff member whatever their role holds, and a role
-* name would refuse a custom role that holds the permission. The rule is given
+* The grant is checked before a collection's rule, and the rule only narrows
+* it, so this check repeats the gate's and keeps the default plain; a role
+* name here would refuse a custom role that holds the permission. The rule is given
 * the caller's permissions as the role screen spells them, `<action>-<slug>`,
 * for a session and an API key alike, and a visitor holds none. `collection` is the slug the host installed
 * the collection under, so a renamed collection is judged by its own