Builder / Repeater field support

[piotrku]

Filament Version

v.3.2.x

Plugin Version

v3.7.3

PHP Version

PHP 8.3.x

Problem description

Hi, I suppose this is not supported (yet?) or I'm doing something wrong.
I want my media to be kept in the media / media_items table.
This is because I use this Repeater in a (Filament) Builder::make('content_flexible') where content_flexible is a one big JSON field to hold all the Builder Blocks content, so I need more flexibility and cannot create a separate image field for each image.

So I'm using here the MorphAble approach and Repeater to create slides. I use maxItems(1) to limit one image per slide but still using MorphAble.

Repeater::make('slides')
    ->schema([
        TextInput::make('label'),
        CuratorPicker::make('Slide media')
            ->multiple()
            ->relationship('media', 'id')
            ->typeValue('slide_media')
            ->maxItems(1),
])

The problem here is that all images for this slider end up in the media_items table with the same typeValue('slide_media') so I end up with one image because all have the same typeValue - is there some workaround this issue?

Expected behavior

I'd like to have a mechanism for automatic typeValue() generation - so the images within the repeater could be uniquely identified.
I tried to use Closure to put some dynamic value her typeValue() but that ends with an error that string is required and Closure is allowed.

Steps to reproduce

Try to use the CuratorPicker with MorphAble with a Repeater or Block when using the same block type with CuratorPicker multiple times.

Reproduction repository

No response

Relevant log output

[awcodes]

I've never even heard of the typeValue method? What does it do?

[awcodes]

Ok found it. Must have been from a PR, will have to research more to figure it out again.

[awcodes]

Haven't forgotten about this. But I think there is an issue where builders and repeaters can be based on a relationship but don't fully support relationships in their data since they are stored as json data in a single db field if each item isn't a relationship at the builder / repeater form field level.

[renebakx]

I'am running into the same challenge, I want to use a Curator field on a Builder instance and I haven't heard nor read about the typeValue() function neither.

For my use case it would be fine if I can just store the Media.In In the json output of builder field.

If someone can point me a bit in the right direction I could spend a bit of time on it to see if we can make it work by some form of faking that relation from a JSON structure.

[piotrku]

@renebakx it IS stored in media_items - no problem - just use the multiple() and relationship('media'... - this part is easy:

Repeater::make('slides')
                ->schema([
                    TextInput::make('title')
                        ->required(),
                    CuratorPicker::make('Slide media')
                        ->multiple()
                        ->relationship('media', 'id')
                        ->typeValue('header_slider')
                        ->maxItems(1)
                        ->acceptedFileTypes(['image/jpeg', 'image/png', 'image/webp', 'video/webm', 'video/mp4']),
                ])

unfortunately things get complicated because all the repeater items get the same type value (header_slider here) and because of that only one image for all items ends in the media_items table.

When not using repeaters you can provide unique ->typeValue( so each media from this page gets a unique entry in the media_items table. But with a repeater - the problem is that the argument for ->typeValue() needs to be a string - I thought I could provide a Closure here to somehow add the uniqueness but only strings are accepted.

So I'm kind of stuck, when I find some solution I will post it here.