As for comments I usually just make keys named something like 'Comment' with a string value of the comment, things ignore unknown keys (thus far), however elm package has the nasty habit of cleaning the elm-package.json of unknown keys (which sucked when a package I was using was trying to story elm config data in the elm-package.json, they eventually ended up making a new file because elm kept wiping their configs). Something better that supports comments would be very useful though, it is surprising how often it comes in hand, however they will still be wiped with elm package reparsed and wrote it out again.
On Wednesday, September 14, 2016 at 9:17:56 AM UTC-6, suttlecommakevin wrote: > > Since npm has struggled with issues like org scoping + multiple registries > <https://github.com/npm/registry/issues/19>, and comments inside of > package.json <https://github.com/npm/npm/issues/4482>, > I'm hoping there has been enough forethought put into this file format to > avoid the same problems. > > *Related: > https://groups.google.com/forum/#!msg/elm-discuss/4GzZKlkyb3w/-NSfk7IpCQAJ;context-place=forum/elm-discuss > > <https://groups.google.com/forum/#!msg/elm-discuss/4GzZKlkyb3w/-NSfk7IpCQAJ;context-place=forum/elm-discuss>* > > > > > -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
