Twill

since there is no way to pass a value to a field from blade, it needs to be returned in the form fields data or from a model accessor

add a function in the repo? 
```
public function getFormFields($object)
    {
        $fields = parent::getFormFields($object);
        $fields = $this->getFormFieldsForRepeater($object, $fields, 'members', 'TeamMember', 'team-member');
        return $fields;
    }
```

```php
public function getFormFields($object) {
    $fields = parent::getFormFields($object);

    $fields['user_name'] = User::find($object->user_id)?->name;

    return $fields
}
```

In the form:
```
@formField('input', [
    'name' => 'user_name',
    'label' => 'User name',
    'disabled' => true
])
```

wow, that worked instantly, thanks a lot 😁

Or alternative to this, you can append property to the model and resolve it directly in the model. Twill will handle it automaticly by name `user_name` which is appended to the model.

Using `$indexColums` in your module controller

Hi is there a way in twill 3 to add my own custom statuses and change this in the CMS to something that is more usefull for orders.

Thats where I added these, but they dont show on the table row itself

Override `getSubmitOptions` in your module controller

of course 
```
    protected $indexColumns = [
        'title' => [ 
            'title' => 'Title',
            'field' => 'title',
        ],
        'User Name' => [
            'title' => 'User Name',
            'field' => 'user_name',
            'sort' => true,
        ],
        'User Email' => [
            'title' => 'User Email',
            'field' => 'user_email',
            'sort' => true,
        ],
    ];
```

Did you define `getUserNameAttribute()` and `getUserEmailAttribute()` in the model behind this controller?

there's no way for twill to understand that it's supposed to find the user from the id in your table without those accessors

not yet, thats why im asking because I had no idea what i supposed to do

also I'm afraid sort won't work by default with such case. You will need to implement a custom `order` method in the repository to order by a custom key. Without that the only thing it would know how to sort on would be the id column, since that's the only on in your model

thats no big deal if I can fix it just like before (adding a function in the repo)

```php
public function getUserNameAttribute() 
{
    return User::find($this->user_id)?->name;
}
```

```php
public function getUserEmailAttribute() 
{
    return User::find($this->user_id)?->email;
}
```

I would create a third function to avoid repeating yourself

and yes the order function is to override in the repository

you will need to add the `sortKey` parameter to your indexColumns columns, and use that in the order function to order by it

Question for you though, why don't you have a user() relationship in your model?

since you're storing a foreign key id for it

I forgot it, I started doing the forms and got sidetracked