fix: use nlohmann::json::boolean_t wrapper for bool conversion

[timblaktu]

Fix: Use nlohmann::json::boolean_t wrapper for bool conversion

Problem

When building docling-parse with nlohmann_json in a C++20 environment, the template resolution fails with the error:

error: 'bool' is not a class, struct, or union type

This occurs because C++20's stricter template instantiation rules conflict with nlohmann_json's SFINAE-based type detection when directly assigning a bool value to a nlohmann::json object.

Root Cause

The issue arises in src/v2/qpdf/to_json.h where we directly assign a boolean value:

bool val = obj.getBoolValue();
result = val;  // This fails template resolution in C++20

The nlohmann_json library uses SFINAE (Substitution Failure Is Not An Error) patterns to detect and handle different types. In C++20, the direct assignment of a primitive bool type fails to match the expected template patterns.

Solution

Use nlohmann::json's boolean_t wrapper type, which is specifically designed to handle boolean values in the JSON library's type system:

bool val = obj.getBoolValue();
result = nlohmann::json::boolean_t(val);  // Explicit wrapper for proper conversion

This ensures proper template resolution by providing a type that nlohmann_json's SFINAE patterns can correctly identify and handle.

Testing

This fix has been tested with:

• nlohmann_json 3.11.x and 3.12.x
• C++17 and C++20 compilation modes
• NixOS build environment with comprehensive dependency checking

The change is minimal, backwards-compatible, and follows nlohmann_json's recommended practices for type conversion.

Impact

• Fixes build failures in C++20 environments
• Maintains backward compatibility with C++17
• No functional changes to the library behavior
• Enables docling-parse to work with modern C++ standards

Fixes build issues reported in various package managers including NixOS/nixpkgs.

[github-actions]

❌ DCO Check Failed

Hi @timblaktu, your pull request has failed the Developer Certificate of Origin (DCO) check.

This repository supports remediation commits, so you can fix this without rewriting history — but you must follow the required message format.

---

🛠 Quick Fix: Add a remediation commit

Run this command:

git commit --allow-empty -s -m "DCO Remediation Commit for Tim Black <[email protected]>

I, Tim Black <[email protected]>, hereby add my Signed-off-by to this commit: a652fd3fa090db52094ab824c78723214826a752
I, Tim Black <[email protected]>, hereby add my Signed-off-by to this commit: f099a24117b44af1c27cfe604fa71ec0c7fb2137
I, Tim Black <[email protected]>, hereby add my Signed-off-by to this commit: 415e39f8452e005be02126badfb7c2960388bed8
I, Tim Black <[email protected]>, hereby add my Signed-off-by to this commit: 7ced0d2a1fbee9914d0cdb04f11275a523cf0a82
I, Tim Black <[email protected]>, hereby add my Signed-off-by to this commit: 95b3ac926ecf5f40922c52c4d82ba7ffb81c7acf
I, Tim Black <[email protected]>, hereby add my Signed-off-by to this commit: 10279e429ae5cc2903eec806b13a414032f6ae59
I, Tim Black <[email protected]>, hereby add my Signed-off-by to this commit: 1f5d11628a5b0509aec1b971d959404582ca5531"
git push

---

🔧 Advanced: Sign off each commit directly

For the latest commit:

git commit --amend --signoff
git push --force-with-lease

For multiple commits:

git rebase --signoff origin/main
git push --force-with-lease

More info: DCO check report

[mergify]

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🟢 Enforce conventional commit

Wonderful, this rule succeeded.

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

• title ~= ^(fix|feat|docs|style|refactor|perf|test|build|ci|chore|revert)(?:\(.+\))?(!)?: