https://github.com/melpa/melpa/pull/5888 demonstrates how json-encode messes up the value of the :files property of recipes. IMO we should not do what's proposed in that pr and just refrain from trying to turn the value :files into json, by storing the complete value as a single string in json.
@conao3 Do you actually have to extract the value of :files out of the json file? Unless someone actually needs to get this data from there I see no reason to go through all the trouble that encoding this in json would bring with it. (I don't think your proposed pr would be sufficient.)
https://github.com/melpa/melpa/pull/5888 demonstrates how
json-encode
messes up the value of the:files
property of recipes. IMO we should not do what's proposed in that pr and just refrain from trying to turn the value:files
into json, by storing the complete value as a single string in json.Replace
(which is invalid) with
@conao3 Do you actually have to extract the value of
:files
out of the json file? Unless someone actually needs to get this data from there I see no reason to go through all the trouble that encoding this in json would bring with it. (I don't think your proposed pr would be sufficient.)