fix(doc): TOML otel exporter example — multi-line inline table is inv… #7669
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.
…alid (#7668)
The
otelexporter example indocs/config.mdis misleading and will causethe configuration parser to fail if copied verbatim.
Summary
The example uses a TOML inline table but spreads the inline-table braces
across multiple lines. TOML inline tables must be contained on a single line
(
key = { a = 1, b = 2 }); placing newlines inside the braces triggers aparse error in most TOML parsers and prevents Codex from starting.
Reproduction
~/.codex/config.toml(or your project config).codex(or the command that loads the config).Problematic snippet (as currently shown in the docs)
Recommended fixes
Or, keep an inline table but write it on one line (valid but less readable):