Re: [go-nuts] Re: When will the official encoding/json package support parsing json5？

On Mon, Mar 21, 2022 at 6:00 AM jan.f...@gmail.com wrote: > Just googled for "json5 golang" and there seem to be several 3rd party > implementations available. > Can you not use one of those? See also HuJSON, also known as "JSON With Commas and Comments": https://github.com/tailscale/hujson

[go-nuts] Re: When will the official encoding/json package support parsing json5？

Just googled for "json5 golang" and there seem to be several 3rd party implementations available. Can you not use one of those? söndag 20 mars 2022 kl. 14:27:05 UTC skrev Brian Candler: > If you're going down that route, you could also consider jsonnet > (which does have

[go-nuts] Re: When will the official encoding/json package support parsing json5？

If you're going down that route, you could also consider jsonnet (which does have a Go implementation ) It will almost certainly be much more powerful than you need, but it *is* another superset of JSON which includes comments. On

[go-nuts] Re: When will the official encoding/json package support parsing json5？

You might want to try qjson that I wrote a year ago (https://github.com/qjson). It's basically just one function that converts qjson text into json. Qjson is inspired by hjson, but extend it in many ways. It is convenient for config files. Maybe I extend it a bit too far by supporting

[go-nuts] Re: When will the official encoding/json package support parsing json5？

Yeah, Go's encoding/json will almost certainly never support json5. However, one very simple approach: if you're using JSON for a config file and just need ability to add // line comments, you can just write a simple transformer which reads the file line by line and filters out lines that

[go-nuts] Re: When will the official encoding/json package support parsing json5？

It is my sincere hope that Go will never support anything as poorly designed as JSON5, using reflection is already slow enough. Comments were never intended for JSON and never should be added, ever. But since most discerning development shops are moving to Protobuf for everything that matters,