* [YAML provider] Add INFO log for config TEXT param value not parsed as string
Related to openhab/openhab-webui#3696
Follow-up #5248
A log at level INFO is now displayed when a YAML file is loaded and contains a thing or channel configuration parameter of type TEXT whose value is not parsed as a string. This occurs when an unquoted number is provided. The log recommends enclosing the value in double quotes to prevent conversion.
For better consistency, the YAML provider is now also processing any BigDecimal value to convert it into a String type when the config paramater is of type TEXT.
Signed-off-by: Laurent Garnier <lg.hc@free.fr>
* Upgrade pdfbox from to 3.0.1
Upgrade Apache pdfbox from 2.0.27 to 3.0.1.
* Exclude junit due to launcher incompatibility
Signed-off-by: Holger Friedrich <mail@holger-friedrich.de>
Upgrade com.jayway.jsonpath:json-path from 2.9.0 to 2.10.0,
including the following dependencies:
Upgrade net.minidev:accessors-smart and net.minidev:json-smart to from 2.5.0
to 2.6.0. Removes transitive CVE-2024-57699.
Signed-off-by: Holger Friedrich <mail@holger-friedrich.de>
Fixes#4395.
The issue was noticed for Rules DSL, but not for JS Scripting, because JS Scripting is loaded at a point where the rule engine is already started.
Signed-off-by: Florian Hotze <dev@florianhotze.com>
This PR normalizes thing/channel configuration before producing the response.
It allows having proper types for config parameters in the JSON response of the API.
Signed-off-by: Laurent Garnier <lg.hc@free.fr>
* [YAML provider] Add special handling to thing/channel config param of type text
Related to openhab/openhab-webui#3696
For configuration parameter of type text only, if the value in YAML is an unquoted number (value is then of type BigDecimal after loading and mapping in our DTO) and there is no decimal, we convert it to an integer and return a String from that integer.
Value 1 in YAML is converted into String "1"
Value 1.0 in YAML is converted into String "1"
Value 1.5 in YAML is untouched
Value "1" in YAML is untouched
Value "1.0" in YAML is untouched
Value "1.5" in YAML is untouched
All this is to avoid that 1 filled in YAML without quotes finally results in string "1.0" after configuration normalization.
Signed-off-by: Laurent Garnier <lg.hc@free.fr>
Related to openhab/openhab-webui#3696
We setup our YAML generator library to use quotes for strings when the value is a number.
Strings being not a number will still be generated without quotes.
It avoids later when parsing the generated YAML to retrieve a BigDecimal type instead of a String type when the DTO is defined with a Java Object type (that is the case for thing/channel configuration in particular).
Signed-off-by: Laurent Garnier <lg.hc@free.fr>
Ideally these should be rewritten to avoid relying on setting the defaults, but for now an effort is done to make sure that the initial value is restored after testing, and that
these tests don't run in parallel with other tests.
Signed-off-by: Ravi Nadahar <nadahar@rediffmail.com>
* Upgrade Karaf to 4.4.9
Upgrade Karaf from 4.4.8 to 4.4.9.
This includes upgrades for the following libraries:
* jetty from 9.4.57.v20241219 to 9.4.58.v20250814
* pax-web from 8.33 to 8.34
* asm from 9.8 to 9.9
* bouncycastle/bcprov from 1.81 to 1.83
* classgraph from 4.8.180 to 4.8.184
* commons-cli from 1.9.0 to 1.10.0
* commons-io from 2.20.0 to 2.21.0
* commons-lang3 from 3.18.0 to 3.20.0
* cxf from 3.6.8 3.6.9
* guava from 33.4.8-jre to 33.5.0-jre
* jackson-annotations from 2.19.2 to 2.20
* jackson from 2.19.2 to 2.20.1
* jna from 5.17.0 to 5.18.1
* ws.xmlschema from 2.3.1 to 2.3.2
* xbean from 4.27 to 4.28
* xtext/xtend from 2.40.0 to 2.41.0
Signed-off-by: Holger Friedrich <mail@holger-friedrich.de>
* New translations automation.properties (Czech)
* New translations messages.properties (Czech)
* New translations messages.properties (Dutch)
* New translations automation.properties (Dutch)
* New translations defaultsystemchannels.properties (Czech)
* New translations addons.properties (Czech)