wip

Author: pxpm

7.x-dev/base-components.md

@@ -97,7 +97,6 @@ This component helps you show a form _anywhere you want_, so the admin can easil
 ```
 
 **Configuration options:**
-- `name='invoice_form'` - by default, a name will be generated; but you can pick one you can recognize;
 - `operation='create'` - by default, the datatable component will pick up everything that controller sets up for the Create operation; if you want to change the operation it will initialize, you can pass this parameter;
 - `:entry="\App\Models\Invoice::find(1)"` - if you want to use UpdateOperation or a custom form operation that needs the entry;
 - `:setup="function($crud, $parent) {}"` - if you want to make changes to the operation setup (eg. add/remove fields, configure functionality), you can use this parameter; the closure passed here will be run _after_ the setup of that operation had already completed;
@@ -123,16 +122,17 @@ This component helps you show a form _anywhere you want_, so the admin can easil
 
 ![Backpack v7 Dataform Modal component](https://backpackforlaravel.com/uploads/v7/dataform_component.jpg)
 
-This component helps you show a form _anywhere you want_ inside a modal, so the admin can easily create or edit an entry for an Eloquent model without having to refresh the whole page. The dataform modal component is a extension of a CrudController - so a CrudController for that entity needs to be already set up, and passed to this component as a parameter:
+This component helps you show a form _anywhere you want_ inside a modal, so the admin can easily create or edit an entry for an Eloquent model without having to refresh the whole page.
+
+To use this component you are required to add `CreateInModalOperation` and/or `UpdateInModalOperation` in your CrudController. The dataform modal component is a extension of a CrudController - so a CrudController for that entity needs to be already set up, and passed to this component as a parameter:
 
 ```html
 <x-bp-dataform-modal controller="\App\Http\Controllers\Admin\InvoiceCrudController" />
 ```
 
 **Configuration options:**
-- `name='invoice_form'` - by default, a name will be generated; but you can pick one you can recognize;
-- `operation='create'` - by default, the datatable component will pick up everything that controller sets up for the Create operation; if you want to change the operation it will initialize, you can pass this parameter;
-- `:entry="\App\Models\Invoice::find(1)"` - if you want to use UpdateOperation or a custom form operation that needs the entry;
+- `operation='createInModal'` - by default, the component will pick up everything that controller sets up for the Create operation; if you want to change the operation it will initialize, you can pass this parameter, eg: `updateInModal`
+- `:entry="\App\Models\Invoice::find(1)"` - if you want to use UpdateInModalOperation or a custom form operation that needs the entry;
 - `:setup="function($crud, $parent) {}"` - if you want to make changes to the operation setup (eg. add/remove fields, configure functionality), you can use this parameter; the closure passed here will be run _after_ the setup of that operation had already completed;
 
 **Advanced example:**
@@ -141,7 +141,7 @@ This component helps you show a form _anywhere you want_ inside a modal, so the
 <x-bp-dataform-modal
     controller="\App\Http\Controllers\Admin\InvoiceCrudController"
     name="invoice_form"
-    operation="update"
+    operation="updateInModal"
     :entry="\App\Models\Invoice::find(1)"
     :setup="function($crud, $parent) {
         $crud->removeColumn('notes');
@@ -150,7 +150,7 @@ This component helps you show a form _anywhere you want_ inside a modal, so the
 ```
 <hr>
 
-> **NOTE**: The tinymce and date_picker (jquery version) does not properly work in this context. Please use any alternative. 
+> **NOTE**: The date_picker (jquery version) does not properly work in this context. Please use any alternative. 
 
 <a name="datatable"></a>
 ### Datatable