thanks for your feedback @fabian, @wolfgang!
so the consensus seems to be to simply expose the array in the api schema and
always have the client send the whole array over, like in pbs updater
(not a problem for my series, since in the gui we have the whole info anyway,
also if one want a custom
On Wed, May 10, 2023 at 01:48:11PM +0200, Fabian Grünbichler wrote:
> On May 10, 2023 10:18 am, Dominik Csapak wrote:
> > @@ -124,6 +130,24 @@ sub updateSchema {
> >
> > next if defined($filter_type) && !defined($copts->{$p});
> >
> > + if ($propertyList->{$p}->{type} eq 'array') {
> > +
On May 10, 2023 10:18 am, Dominik Csapak wrote:
> enables section configs in the style of:
>
>
> type: id
> property value
> property value2
> property value3
>
>
> can be combined with property strings
>
> the provided createSchema just uses the name of the property but th
enables section configs in the style of:
type: id
property value
property value2
property value3
can be combined with property strings
the provided createSchema just uses the name of the property but the
schema of the inner item
the api call is supposed to check if the ove
