A field to handle inline CRUD operations. It can be used with either an embeds_many or has_many (association) type column.

Field-specific options

See Backpex.Field for general field options.

• :type - Required. The type of the field.

• :child_fields (keyword/0) - Required. A list of child input fields.

  The following fields are not supported:

  • Backpex.Fields.HasManyThrough
  • Backpex.Fields.InlineCRUD
  • Backpex.Fields.Upload

  You can add additional classes to child field inputs by setting the class option in the list of child_fields. The class can be a string or a function that takes the assigns and must return a string.

EmbedsMany

The field in the migration must be of type :map. You also need to use ecto's cast_embed/2 in the changeset.

Example

def changeset(your_schema, attrs) do
  your_schema
  ...
  |> cast_embed(:your_field,
    with: &your_field_changeset/2,
    sort_param: :your_field_order,
    drop_param: :your_field_delete
  )
  ...
end

HasMany (Association)

A HasMany relation does not require any special configuration. You can simply define a basic Ecto.Schema.has_many/3 relation to be used with the Backpex.Fields.InlineCRUD field.

Example

@impl Backpex.LiveResource
def fields do
  [
    embeds_many: %{
      module: Backpex.Fields.InlineCRUD,
      label: "EmbedsMany",
      type: :embed,
      except: [:index],
      child_fields: [
        field1: %{
          module: Backpex.Fields.Text,
          label: "Label1"
        },
        field2: %{
          module: Backpex.Fields.Text,
          label: "Label2"
        }
      ]
    }
  ]
end