controller instead of model in config_relation

[SledgehammerPL]

Model:
document
id|issuer_id|document_date|document_number

person
id|last_name

and I create two controllers: documents nad people which shows list of documents (with last_name of issuer) and people.

But I want to go further. If I choose person of people's list I will go to field.yaml which shows last_name AND the list of documents issued by this person.

But the list uses model not controller.

of course because it is set in config_relation.html of people's controller.

documents:
  label: Documents
  view:
    list: $/party/structure/models/document/columns.yaml
    toolbarButtons: create
    showSorting: false
    defaultSort:
      column: document_date
      direction: desc
  manage:
    form: $/party/structure/models/document/fields.yaml

But I need controller. Because I use ExtendedQuery and ExtendedScope in controller.
How to use controller instead of model?

[SledgehammerPL]

if you use list - the controller uses public function ListExtendQuery($query)
If you use form - the controller uses public function FormExtendQuery($query)

BUT THERE'S A BUG!

if You use addSelect with ListExtendQuery it works as expected. But addSelect with FormExtendQuery has a little bug

You have to add
$ model Name = (new Model)->getTable();
$query->addSelect($ model Table.'.*');

because if not you would got only added fields - no basic fields....

But it isn't what I want. It is very useful if you want to add some information in top part of form, but I have tabs with partials. But that queries are defined elsewhere.. Not know yet.

[LukeTowers]

@SledgehammerPL I'm not sure what exactly you're trying to do, could you explain it further and / or add screenshots?

[SledgehammerPL]

My models have to use left join instead of inner join, so i have to use List/FormExtendQueries.

[LukeTowers]

That doesn't really clear anything up for me. If you're trying to get at the lists widget provided by the RelationController then take a look at the Relation Controller docs: https://wintercms.com/docs/backend/relations#extend-view-widget about how to extend the view widget and then use that to bind to the list.extendQuery event on the view widget in the appropriate context.

[SledgehammerPL]

It looks promising!