vixcpp/vix

Summary Review the JSON documentation and examples to ensure they match the final public contracts. Current behavior The module contains extensive header documentation, a README, examples, benchmark reports, and a changelog. Some behavior requires clearer or unified documentation, including: Simple ownership and copy semantics; integer range behavior; JPath mutation behavior; file replacement guarantees; safe API error suppression; ordered versus unordered builders; literal macro configuration; parsing and serialization limits. Expected behavior Users should be able to understand the module’s two JSON models and choose the correct API without reading implementation details. Scope Explain Json versus Simple. Explain when to use each model. Document Simple ownership semantics. Document numeric limits. Document JPath read and write differences. Document file-write guarantees. Document safe and strict error models. Document builder return types. Document dependency requiremen

Summary Add compile tests ensuring each public JSON header includes everything required for independent use. Current behavior The module exposes: build.hpp; convert.hpp; dumps.hpp; jpath.hpp; json.hpp; loads.hpp; Simple.hpp. Headers are often included through the umbrella header, which can hide missing direct dependencies. Expected behavior Every public header must compile as the first and only Vix JSON include in a translation unit. Scope Add one compile target per public header. Compile with GCC. Compile with Clang. Compile with MSVC. Test with strict warnings. Test normal literal configuration. Test enabled literal configuration. Test standalone installation headers. Preserve header-only usage. Suggested files modules/json/tests/headers/build_header_test.cpp modules/json/tests/headers/convert_header_test.cpp modules/json/tests/headers/dumps_header_test.cpp modules/json/tests/headers/jpath_header_test.cpp modules/json/tests/headers/json_header_test.cpp modules/json/test

Summary Prevent the JSON module from unexpectedly changing global CMake variables in parent projects and umbrella builds. Current behavior The module sets global variables such as: CMAKE_CXX_STANDARD; CMAKE_CXX_STANDARD_REQUIRED; CMAKE_POSITION_INDEPENDENT_CODE; CMAKE_RUNTIME_OUTPUT_DIRECTORY. A submodule should generally express requirements through its targets rather than altering unrelated parent targets. Expected behavior The JSON module should use target-scoped configuration wherever possible. Standalone build defaults may still be configured without polluting umbrella consumers. Scope Remove unnecessary global C++ standard changes. Keep target_compile_features() as the public requirement. Review global position-independent-code settings. Review runtime output directory changes. Scope example output paths locally. Scope test output paths locally. Add parent-project integration tests. Preserve standalone behavior. Suggested files modules/json/CMakeLists.txt modules/jso

Summary Add an opt-in durability mode for applications that require data to reach stable storage before dump_file() returns. Current behavior dump_file() writes, flushes the C++ stream, and renames the temporary file. A stream flush does not necessarily guarantee that data or directory metadata has reached durable storage. A system crash or power loss may still lose the latest write. Expected behavior The module should expose an optional durability policy. Normal writes should remain lightweight by default. Durable mode should use platform-specific synchronization where supported. Scope Define a durability option. Synchronize temporary file data before replacement. Synchronize directory metadata after replacement where required. Add POSIX implementation. Add Windows implementation or documented fallback. Report unsupported behavior clearly. Add integration tests where practical. Preserve default performance. Preserve existing APIs. Suggested files modules/json/include/vix/j

Summary Provide one options structure for string serialization and file output. Current behavior Serialization behavior is configured through positional parameters such as: indentation; ASCII escaping. As additional options are added, positional overloads become harder to read and extend. Expected behavior The module should provide an explicit options type while keeping existing overloads. Scope Define a serialization options structure. Support compact output. Support pretty output. Support indentation width. Support ASCII escaping. Define invalid indentation behavior. Integrate options with dumps(). Integrate options with dump_file(). Preserve current overloads. Add tests. Suggested files modules/json/include/vix/json/dumps.hpp modules/json/tests/json_dumps_options_test.cpp Acceptance criteria Existing positional overloads remain compatible. Options-based compact output works. Options-based pretty output works. ASCII escaping follows the selected option. Invalid