fix: handle null property values in PP XML v69+

[dgehriger]

Problem

Portfolio Performance v69+ can produce XML properties with empty/null text content. For example:

<properties>
  <entry>
    <string>portfolio-chart-details</string>
    <string/>
  </entry>
</properties>

This causes ppxml2db to pass None as the property value to the database, violating the NOT NULL constraint on property.value, resulting in:

sqlite3.IntegrityError: NOT NULL constraint failed: property.value

Users see:

CRITICAL unable to import the Portfolio Performance xml file "Portfolio.xml" (is it saved as "XML with ids"?)

Fix

Coalesce None property values to empty string "" in handle_toplevel_properties, consistent with how parse_configuration already handles this case.

Changes

• patch_ppxml2db.diff: Updated patch to include the null-coalesce fix
• tests/fixtures/empty_null_prop.ids.xml: New test fixture with a null property value
• tests/data/test_pp_portfolio_builder.py: Added regression test

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[ma4nn]

Thanks for your contribution @dgehriger, much appreciated 🙏