You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 0fdccbd
Browse filesBrowse the repository at this point in the historyBrowse files
An otlp file of one request ends in .json, and tfg formats names each ending (#231)
* An otlp file of one request ends in .json, and tfg formats names each ending
An otlp file in the minified or indented layout is one JSON document, and
its name ended in .jsonl - which tells a reader that picks its parser by the
name to read it line by line. A setting can now declare the endings its
values give (format.Property.Extensions), and the engine names every file by
Descriptor.ExtensionFor, once for each target. The bytes of every file are
unchanged, and a name template somebody wrote still wins.
tfg formats otlp prints the endings beside the extension, tfg formats --json
carries them as "extensions" on the setting, the site lists both endings,
and the sentence under formatting says them. Two guards hold the declaration
and the names the engine plans, with three mutation entries.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* build(deps): bump github.com/nicksnyder/go-i18n/v2 from 2.6.1 to 2.7.0
The change Dependabot proposed in #222, with the notices naming the version
the window now links. go-i18n is linked by the window alone.
Between 2.6.1 and 2.7.0: the CLDR v49 plural rules (Vietnamese, Galician
and French move between groups), ParseMessageBytes, and fixes to the goi18n
command. The window speaks English and Polish, whose rules did not change.
go.yaml.in/yaml/v3 moves from 3.0.4 to 3.0.5 in go.sum only - nothing links
it. Both LICENSE files are the same text as in the versions before.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* tfg formats is held to the endings a setting gives, in its text and its JSON
The guards on this change held the names the engine plans, and nothing held
what tfg formats says about them: the card could go back to ".jsonl" alone,
and --json could drop "extensions", with every guard green. A guard now reads
both - the card of otlp with its line written out, and the JSON of every
format whose settings give an ending against what they declare - with two
mutation entries, one for each output.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Detail: "How the file is laid out. record-per-line puts one batch on each line, which is what the OTLP file exporter writes and the file receiver of the OpenTelemetry Collector reads. "+
285
-
"minified and indented make the whole file one request, the body to post to an OTLP endpoint, and a file of that kind is one JSON document whatever its name ends in. "+
284
+
// A file of one request is one JSON document, and .jsonl would
285
+
// tell a reader that picks its parser by the name to read it line
286
+
// by line. docs/ROZSZERZENIE-UKLADU-2026-11-11.md.
Detail: "How the file is laid out. record-per-line puts one batch on each line, which is what the OTLP file exporter writes and the file receiver of the OpenTelemetry Collector reads, and the file name ends in .jsonl. "+
289
+
"minified and indented make the whole file one request, the body to post to an OTLP endpoint, and the file name ends in .json. "+
286
290
"Posted as a body, a file of several lines loses every line after the first in the Collector, and its file receiver reads nothing from an indented file.",
0 commit comments