Twill

because we use translations there are modules that only use translatedAttributes and have zero to none fillable fields

I'm still experimenting with translations so I don't even know if all translatedAttributes must be in fillables or otherwise 😅

the preview don't work with repeaters ? I edit the repeater but don't update in the preview until I save the Page

<@!479379745856028705> , how about your weekend? I hope you had good time.

BadMethodCallException
Call to undefined method App\Models\User::isTranslatable()

when I try to use normal model as twill model.

Hi, i have problem about buckets. Module I use for Bucket is realEstates. Model is RealEstate. Bucket saves the database as realEstates, and i get this error. Does anyone have an idea?

They usually answer as soon as they can, they have their own jobs and lives to live, just be patient. Perhaps they are in different time zone and sleeping rn 😄

... but I have a question too - is it possible to use a browser value as @twillRepeaterTitleField? 
Let's say I choose a Category in a browser which is in a repeater and I want to use the Category name for the repeater title

Hi everyone, give me a sec I'll respond to everyone

If you are manually calling the helpers to use the repeater field, you need to also call `hydrateRepeater` in the hydrate hook for the repeaters to be there during a preview. When you use the `$repeaters` property (https://github.com/area17/twill/blob/377e5e0b27916861caa448ef899ea0e3fbeff648/src/Repositories/Behaviors/HandleRepeaters.php#L32) this is being done automatically for you here: https://github.com/area17/twill/blob/377e5e0b27916861caa448ef899ea0e3fbeff648/src/Repositories/Behaviors/HandleRevisions.php#L21

please read <#811986108820357140> again, you don't need to spam the chat, like <@423826082584723456> said, we have a life too and sometimes even need to sleep.

Can you share your user model again? This method is coming from a trait that is used by Twill's model, so if you're extending it you should have access to it.

did you set up a morph map for your realEstates module?

currently only text fields are supported but <@553620329453584414> said more fields will work there in the future

Hey <@!479379745856028705> & <@!423826082584723456>,

So yes, the dynamic repeater/block titles work are pretty limited now. They work with `text` fields of course, and also `select` fields, but in this case you'll get the selected option value instead of label. It's quite a complex problem with the way everything is laid out but I'm still thinking about how to improve it.

To your question <@!423826082584723456>, here's a little hack to get basic "computed" titles for repeaters.

In the migration, add a dummy field, which won't contain any value:
```
$table->string('computed_title', 200)->nullable();
```

On the model, set an attribute accessor for this field, returning your value for a "computed title":
```
public function getComputedTitleAttribute()
{
    return 'Hello';
}
```

Then in the repeater view:
```
@twillRepeaterTitleField('computed_title')
```

Obviously hacky but hey, maybe this can help 🙂

nice! maybe there's a way to skip the migration too?

Yeah, there's got to be a way but I think this is the most simple way to get this fake field picked up by `getFormFieldsHandleBlocks()` behind the scenes.

Don't really understand what's going on behind the scenes with repeaters and blocks, but I find this as a viable solution

so thanks <@!553620329453584414>! will try in a moment

Can't say I fully understand it either 😆 , but it's fun

Haha yes, I do actively work on Twill but it's deeeeeep 🙂

sometimes when I'm solving something I try to look inside of Twill, but man... it's huge for me
I'm not overall coding beginner but new to Laravel and I started Twill at the same time as Laravel. I have bit of mess in what variable belongs to which system (and also functions, classes and so on)

haha <@553620329453584414> is being modest, his twill skills are deeeeep

ha, that makes sense. Laravel does quite a lot and Twill leverages a lot from it

I believe you both are deeeeeeep Twill skilled lol, no need to be modest

Hello, thanks for your reply <@!479379745856028705>

now I made user model extends from twill model.

that can show the user list on the twill UI.