JSON Lines support
Lassi Kortela
(21 Jan 2020 12:05 UTC)
|
||
Re: JSON Lines support Amirouche Boubekki (21 Jan 2020 15:00 UTC)
|
||
Re: JSON Lines support
Lassi Kortela
(21 Jan 2020 22:47 UTC)
|
||
Re: JSON Lines support
John Cowan
(21 Jan 2020 22:51 UTC)
|
||
Re: JSON Lines support
Lassi Kortela
(21 Jan 2020 23:07 UTC)
|
||
Re: JSON Lines support
John Cowan
(22 Jan 2020 00:11 UTC)
|
||
Pretty-printing JSON
Lassi Kortela
(22 Jan 2020 00:22 UTC)
|
||
Re: Pretty-printing JSON
John Cowan
(22 Jan 2020 02:28 UTC)
|
||
Different kinds of JSON writers, and naming them
Lassi Kortela
(22 Jan 2020 11:52 UTC)
|
||
Re: Different kinds of JSON writers, and naming them
John Cowan
(22 Jan 2020 18:37 UTC)
|
||
Re: Different kinds of JSON writers, and naming them
Lassi Kortela
(22 Jan 2020 22:33 UTC)
|
||
Re: Different kinds of JSON writers, and naming them
John Cowan
(22 Jan 2020 22:44 UTC)
|
||
Re: Different kinds of JSON writers, and naming them
Duy Nguyen
(23 Jan 2020 10:01 UTC)
|
||
Optional features in SRFIs
Lassi Kortela
(24 Jan 2020 15:30 UTC)
|
||
Re: Optional features in SRFIs
Lassi Kortela
(24 Jan 2020 15:35 UTC)
|
||
Re: Optional features in SRFIs
Arthur A. Gleckler
(24 Jan 2020 15:57 UTC)
|
||
Re: Optional features in SRFIs
John Cowan
(24 Jan 2020 17:01 UTC)
|
||
Re: Optional features in SRFIs
Lassi Kortela
(24 Jan 2020 17:07 UTC)
|
||
(missing)
|
||
Re: Optional features in SRFIs
Lassi Kortela
(24 Jan 2020 18:43 UTC)
|
||
Re: Optional features in SRFIs
Lassi Kortela
(24 Jan 2020 17:12 UTC)
|
Le mar. 21 janv. 2020 à 13:05, Lassi Kortela <xxxxxx@lassi.io> a écrit : > > Big thanks to Amirouche for taking up this important job! Thanks! > You mentioned JSON Lines (<http://jsonlines.org>). This is a great file > format for structured logging (where each log entry is written as an > easy-to-parse record instead of a free-form line of text). > > I'd love having a procedure in the SRFI to explicitly write a JSON Line > (i.e. one JSON value containing no literal newlines) to a port. > Something like: > > (json-write-line obj [port]) > > Or if a procedure is added that takes custom rules for the output (e.g. > how many spaces to indent), JSON Lines be a preset for those rules. The code seems easy with the current implementation, but it might be better to provide a helper for that.