How / where to find (breaking) changes when code changes are committed to beta

Topics (not sure which fora)
when not sure where to post, post here and mods will move it to right forum.

Moderators: leecollings, remb0

Post Reply
User avatar
waaren
Posts: 6028
Joined: Tuesday 03 January 2017 14:18
Target OS: Linux
Domoticz version: Beta
Location: Netherlands
Contact:

How / where to find (breaking) changes when code changes are committed to beta

Post by waaren »

@developers, @gizMocuz,

Thank you for the excellent product you are working on. I really love it !!

While working on a script I noticed that one api call did returned a different json as before. In this case it was
the /json.htm?type=command&param=getlog call.
In Beta's after V3.9580 or around that, an additional setting was required ( loglevel=2 for Status or loglevel=4 for Error ) to get the required information. With the help of @jvdz who digged in the code and monitored the webrequests we managed to find what was needed and I updated the wiki with that information.
I know that I cannot rely on beta to be as stable as the stable version but still would like to be able to see some of these breaking changes comming.
My question: is there an agreed place where developers can share this information with colleagues and users to prevent that code will break unnoticed ?
Debian buster, bullseye on RPI-4, Intel NUC.
dz Beta, Z-Wave, RFLink, RFXtrx433e, P1, Youless, Hue, Yeelight, Xiaomi, MQTT
==>> dzVents wiki
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest