Twill

this will be the new nested repeater button design

Hi guys! I wonder if this is by design that the single checkbox returns checked value as an array?

```@formField('checkbox', [
            'name' => 'featured',
            'label' => 'Featured'
        ])```

I'm trying to use the checkbox field in the settings section and it seems like the returned array breaks the SettingController::update() method.

Yeah you were correct. it was not configured correctly. Works now and works in Glide

hi, how can i use Twill's email layout for my custom emails?

Hi <@682920829499342878> you should be able to use the layout as a component in your app's email views: `@component('twill::emails.html.layout') ... @endcomponent`

Hi <@293033790471929856> this is probably an issue specific to settings. Not all fields are correctly supported there, but our goal is that they all should be, even more complex fields like browser, repeater and block editor.

hi <@!479379745856028705>, i tried this but css file is not working. So this is not enough. I copied Twill's "default.css" file to my own folder and I added `public $template = 'twill.css';` to my Mail class and it worked.

Hello together,
i was just deploying the Twill-Update to our Test-System and got this Error on 
`php artisan view:cache`

` The "/var/www/app/Twill/Capsules" directory does not exist.`

Got it. Just created and commited this directory...

I think this should be generated automatically on `twill:update`

thanks for flagging. I think this should not be required, actually

do you mean you ran into the same issue? Or you agree it should not be required to have this empty folder in your app? Or both? 😉

<@!335827131655520257> <@!140046459889385472> can you try `2.x-dev`? just pushed: https://github.com/area17/twill/commit/5a086a32d04e3889731ce547aa6b673e883ab1ce

We are creating and updating Models programaticly. And i am now wondering if there is a way to make revision work with it?

hi <@!170475091711361024> sure, that should be doable. revisions are storing the json submission from the frontend though, so you might have to look into how they look when changing from the UI to reconstruct them programmatically

or, create and update models through the module's repository

I did try it this way and i am not understanding how to pass a translated field to the create function to not get the error that a translated field is not set.

```
'yourFieldName' => [
  'en' => 'value',
  'anotherLanguage' => 'valueTranslated'
]

```