Skip to content

feat(config): add optional JSON frontend - #162

Open
LimiNode wants to merge 2 commits into
mainfrom
feat/config-json-frontend
Open

LimiNode wants to merge 2 commits into
mainfrom
feat/config-json-frontend

Conversation

@LimiNode

Copy link
Copy Markdown
Owner

Summary

  • add an optional nlohmann::json frontend for ConfigurationDocument
  • keep parsing separate from validation, materialization, binding, and runtime instantiation
  • propagate the optional dependency through CMake and pkg-config package exports
  • document the feature scope in English and Russian

Validation

  • configuration_json_test
  • default Windows test suite: 62/62 passed
  • JSON-enabled installed CMake package consumer
  • generated pkg-config metadata audit
  • git diff --check

Out of scope

  • file I/O helpers
  • properties frontend
  • hot reload

Map JSON text and nlohmann::json values into the parser-neutral configuration document without runtime side effects. Propagate the optional dependency through CMake and pkg-config packages, add focused tests and Linux CI coverage, and document the supported scope.
Make installed-package and pkg-config consumers fail at compile time when the optional JSON feature macro is not exported. Clarify that JSON conversion diagnostics are distinct from backend semantic validation performed during materialization.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant