Remove _design/custom from controller with 4.0

[Apollon77]

And before that update all relevant adapters to use sytem/custom

[foxriver76]

Is there an overview of relevant adapters? And with system custom they will need controller 3.3 as dep

[Apollon77]

The following adapter cvurrently define the "old" _design/custom:

• ioBroker.fullcalendar/io-package.json: "_id": "_design/custom",
• ioBroker.history/io-package.json: "_id": "_design/custom",
• ioBroker.influxdb/io-package.json: "_id": "_design/custom",
• ioBroker.lovelace/io-package.json: "_id": "_design/custom",
• ioBroker.mqtt-client/io-package.json: "_id": "_design/custom",
• ioBroker.powermonitor/io-package.json: "_id": "_design/custom",
• ioBroker.sourceanalytix/io-package.json: "_id": "_design/custom",
• ioBroker.sql/io-package.json: "_id": "_design/custom",
• ioBroker.statistics/io-package.json: "_id": "_design/custom",
• ioBroker.telegram/io-package.json: "_id": "_design/custom",

Additionally the following are using a custom objectView

• ioBroker.upnp/main.js
• ioBroker.valuetrackerovertime/main.js
• pot. ioBroker.zigbee

[foxriver76]

as i see the ones who are defining the design object view themself are not critical, so only upnp, valuetrackerovertime and zigbee needs update with system custom and controller 3.3. as dep

[foxriver76]

upnp fixed -> 1.0.20
Jey-Cee/ioBroker.upnp@0cafffa
valuetracker: Omega236/ioBroker.valuetrackerovertime#22

in zigbee I found nothing via grep

[Apollon77]

In fact all should remove the "self defined" view and migrate to the new system/custom one AND increase their js.controller dep

[foxriver76]

Yes but as long as they are bringing the object themselves they will work like before. But yes we can create issues or prs too if necessary

[foxriver76]

I've created issues for all adapter except ioBroker.powermonitor, which is not in Repo and I also cannot find it on GH