https://bugs.kde.org/show_bug.cgi?id=487212

Nicolas Fella <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
      Latest Commit|                            |https://invent.kde.org/fram
                   |                            |eworks/kconfig/-/commit/083
                   |                            |137a64c8415c71545a6e47fa19b
                   |                            |0aa743409d
             Status|ASSIGNED                    |RESOLVED

--- Comment #5 from Nicolas Fella <[email protected]> ---
Git commit 083137a64c8415c71545a6e47fa19b0aa743409d by Nicolas Fella.
Committed on 09/09/2026 at 10:49.
Pushed by nicolasfella into branch 'master'.

Fix writing empty path entries

putData() behaves differently when adding null vs empty data.

Null means that the entry will be marked as deleted, empty means
an empty value will be written.

When calling write(Path)Entry with an empty string/path we want the
empty entry to be written. To make this work writeEntry() checks
whether the provided value is null and puts an non-null but empty
bytearray in the map. writePathEntry was missing that though, so it
worked as expected for strings but not paths.

M  +9    -0    autotests/kconfigtest.cpp
M  +2    -2    src/core/kconfiggroup.cpp

https://invent.kde.org/frameworks/kconfig/-/commit/083137a64c8415c71545a6e47fa19b0aa743409d

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to