Patrik Duditš

A change of README file is also an example that shouldn't cause all modules to be released.

Same problem persists on latest version: Home Assistant 2023.5.2 Supervisor 2023.04.1 Operating System 10.1 Frontend 20230503.3 - latest ESPHome version 2023.4.4 Win 10, Edge, also a ESP8266 based device.

Turns out it is related to this note in Template select documentation: > If you don’t set a lambda and optimistic is false (default), updates to the select component state...

One more step to symmetry would be to allow `Jsonb.toJson` accept null input. The new section 3.14.3 can also specify: "Serialization of Java null value results in JSON Document `null`".

> But please take care null can be desired to be skipped which means that at root level we would have an inconsistency forcing its materialization. The focus of this...

Such behavior is also consistent with Javascript: ```` JSON.stringify(null) > "null" JSON.parse("null") > null JSON.parse("") > SyntaxError: JSON.parse: unexpected end of data ````

With `undefined` we get into one of the strong areas of Javascript -- consistency: ```` JSON.parse("undefined") SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data JSON.stringify(undefined)...

For configurability I can imagine `JsonConfig.withNullSerializer(JsonbSerializer nullSerializer)` It would be called whenever `null` or empty optional is passed to `toJson(T)`. This enables it to serialize as any of the options...

Just tried that, requires Arquillian upgrade as well due to arquillian/arquillian-core#427. But that might affect various downstream TCK test repos, as we don't actually hint arquillian version in the bom...

Jenkins test please