[mythtv] Services API for ChannelServices / Channel

[Gary Buhrmaster]

On Mon, Dec 2, 2019 at 10:20 PM David Engel <david at istwok.net> wrote:

> Also, I don't think the update
> only the chagned values will work in the general case.  It might not
> be possible to validate the changed values without knowing some of the
> unchanged values too.

To pile on a bit.....

It has been my experience that the
current services API, in some cases,
is fundamentally too low level, allowing
one (today) to set values that are (at
best) brain dead, and there is a lack
of business logic consistency applied
to the provided values (and in some
cases there is no way to apply the
proper business logic because those
relationships are not exposed for
add/updates (my pet example is creating
channels that require creation of a new
dtv_multiplexes, but you can't do that
(or you could not when I last checked))).

In essence, some of the API endpoints
are just fancy direct database updates,
with all the (dis)advantages of such.
My codes have had to try to implement
the business logic, and while I have
tried to read the relevant codes, it
could easily be incorrect, and whether
I would notice a change in business
logic in some MythTV commit is a
crap shoot.  This feels excessively
fragile.

Unfortunately, I don't see an easy
way forward (all the ways I think
of require some significant resources).