Model.collections does not need a list of fields
david-pfx opened this issue · 4 comments
In any model collections is the specification of a child set. It is used on a browse screen to retrieve a list of child records displayed in master-detail format.
The fields information is redundant. It matches exactly the fields information in the child model, and can be retrieved as needed by accessing the child model (filtered presumably on inMany). For similar reasons the table and column attributes are also redundant.
...sometimes there is no child model.
How can that be so? There is no such sample, no way to load data without a model and no way to resolve the browse link unless the child has a model.
So by fiat, let it be so, the child must have a model.
I missed one thing: the child field list has the parent entity as a field, which needs to be filtered out.
Changes made. Submitting PR. See what you think.
Fields in collections can now be ids or field objects.