A Log tracer can now write JSON lines (inbuxa-server #456, server PR to follow). For those entries x:Log hands back the event's fields as a JSON object in details instead of key = value text. The Logs page reads that object as written: strings as they are, and numbers, lists and nested events as JSON. Text entries parse as before, and a file holding both reads both.
The JSON export keeps a JSON entry's fields typed instead of turning them into strings.
Against a server without #456 nothing changes: details is never a JSON object there.
Checked locally: typecheck, lint, i18n:check, all 1137 tests (4 new), the three shell tests, build and notice-check.
Part of inbuxa/inbuxa-server#456 (forum t/308).
A Log tracer can now write JSON lines (inbuxa-server #456, server PR to follow). For those entries `x:Log` hands back the event's fields as a JSON object in `details` instead of `key = value` text. The Logs page reads that object as written: strings as they are, and numbers, lists and nested events as JSON. Text entries parse as before, and a file holding both reads both.
The JSON export keeps a JSON entry's fields typed instead of turning them into strings.
Against a server without #456 nothing changes: `details` is never a JSON object there.
Checked locally: typecheck, lint, i18n:check, all 1137 tests (4 new), the three shell tests, build and notice-check.
A Log tracer can write JSON lines (inbuxa-server #456). For those entries
the server hands back the event's fields as a JSON object in `details`
instead of `key = value` text, so the Logs page reads them as written:
strings as they are, numbers, lists and nested events as JSON. Text
entries are parsed as before, and a file holding both reads both.
The JSON export keeps a JSON entry's fields typed rather than as strings.
Test: parseFields and jsonFields on JSON objects, other JSON and plain
text; the export keeps typed fields.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Part of inbuxa/inbuxa-server#456 (forum t/308).
A Log tracer can now write JSON lines (inbuxa-server #456, server PR to follow). For those entries
x:Loghands back the event's fields as a JSON object indetailsinstead ofkey = valuetext. The Logs page reads that object as written: strings as they are, and numbers, lists and nested events as JSON. Text entries parse as before, and a file holding both reads both.The JSON export keeps a JSON entry's fields typed instead of turning them into strings.
Against a server without #456 nothing changes:
detailsis never a JSON object there.Checked locally: typecheck, lint, i18n:check, all 1137 tests (4 new), the three shell tests, build and notice-check.