Repository navigation
Conversation
Instantiate materialized file, memory, OTLP, and Prometheus plans through typed runtime bindings. Keep parsing and default materialization outside the factory and cover optional backend paths in the configuration contract test.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary\n- add a built-in factory for materialized file, unique-file, memory, OTLP, and Prometheus logger plans\n- map materialized fields into typed backend Config values without parsing or new defaults\n- resolve typed on_payload bindings for callback backends and cover optional feature paths\n\n## Validation\n- C++11 focused configuration contract test\n- full baseline CTest: 62/62 passed\n- OTLP configuration contract test passed\n- Prometheus payload and server configuration contract tests passed\n- git diff --check\n\nParser frontends and hot reload remain out of scope.