Myasnikov Daniil 3b83fc17da fix(dashboard): resolve a field whose map key contains a dot ...

Continuing the id namespace into a map entry's nested form put the
literal key into the DOM id, which made a pre-existing gap reachable
with a shipped schema: a mariadb user named john.doe renders
root_users_john.doe_maxUserConnections, while the error path
.users.john.doe.maxUserConnections split into one segment too many and
resolved nothing. The flattened path cannot say whether a dot separates
two properties or sits inside one name, so try the plain split first and
then each way of gluing adjacent segments back together, bounded, taking
the first id that exists. Only exact ids are tried this way; the
descendant fallback stays on the plain split, where it is meaningful.

Assisted-by: LLM
Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>

2026-10-07 05:04:50 +03:00

..

apps

fix(dashboard, kubernetes): declare the no-enable-switch addons and harden the focus helper

2026-10-07 05:04:06 +03:00

core

feat(kubevirt)!: drop HotplugVolumes for declarative volume hotplug (#4453)

2026-10-06 17:06:03 +03:00

extra

fix(monitoring): count a central request as the receiver admitted it

2026-10-06 09:39:04 +03:00

library

fix(cozy-lib): round the sanitized CPU request up to a whole milli-CPU

2026-09-29 17:04:00 +02:00

system

fix(dashboard): resolve a field whose map key contains a dot

2026-10-07 05:04:50 +03:00

tests/cozy-lib-tests

fix(cozy-lib): round the sanitized CPU request up to a whole milli-CPU

2026-09-29 17:04:00 +02:00