mleku on Nostr: haha nip-47 was obviously written by #golang programmers check out the protocol ...
haha
nip-47 was obviously written by #golang programmers
check out the protocol message spec here and hypothetically imagine that it's supposed to be valid JSON (ignore the comments in the discussion for a moment, although they are // comments also
what's wrong with them?
commas on end of every line
in Go you can only skip a comma at the end of a list if the closing brace/parethesis comes before the end of line
technically you almost always minify json, making it one line per message anyway, no linebreaks even where valid, so the same syntax would apply but it's not readable
but, funny... i should maek a PR to make the JSON actually correct, put it inside markdown tables so the comments can be lined up but not part of what you would copy
nip-47 was obviously written by #golang programmers
check out the protocol message spec here and hypothetically imagine that it's supposed to be valid JSON (ignore the comments in the discussion for a moment, although they are // comments also
what's wrong with them?
commas on end of every line
in Go you can only skip a comma at the end of a list if the closing brace/parethesis comes before the end of line
technically you almost always minify json, making it one line per message anyway, no linebreaks even where valid, so the same syntax would apply but it's not readable
but, funny... i should maek a PR to make the JSON actually correct, put it inside markdown tables so the comments can be lined up but not part of what you would copy