)]}'
{"mistral/utils/expression_utils.py":[{"author":{"_account_id":9712,"name":"Dougal Matthews","email":"dougal.matthews@canonical.com","username":"dougal"},"change_message_id":"408e9bc8903b453fda22436499cea34fff783ea3","unresolved":false,"context_lines":[{"line_number":122,"context_line":"    ).replace(\"\\\\n\", \"\\n\").replace(\" \\n\", \"\\n\")"},{"line_number":123,"context_line":""},{"line_number":124,"context_line":""},{"line_number":125,"context_line":"def yaml_dump_(context, data):"},{"line_number":126,"context_line":"    return yaml.safe_dump(data, default_flow_style\u003dFalse)"},{"line_number":127,"context_line":""},{"line_number":128,"context_line":""}],"source_content_type":"text/x-python","patch_set":1,"id":"3f4b6375_7214084f","line":125,"updated":"2017-10-20 07:10:48.000000000","message":"Should this have the same behaviour as json_pp? i.e. the context thing. It seems like a strange feature tbh, but consistency is king.\n\nOn that note... I much much prefer yaml_dump. I wonder if we could rename json_pp to json_dump. I had no idea what json_pp done when I found it originally.","commit_id":"8a0733b9d682de3cf67440bc4c58d60fb1e11356"},{"author":{"_account_id":9712,"name":"Dougal Matthews","email":"dougal.matthews@canonical.com","username":"dougal"},"change_message_id":"6e20aa645c41862341a2078762033a5a75760024","unresolved":false,"context_lines":[{"line_number":122,"context_line":"    ).replace(\"\\\\n\", \"\\n\").replace(\" \\n\", \"\\n\")"},{"line_number":123,"context_line":""},{"line_number":124,"context_line":""},{"line_number":125,"context_line":"def yaml_dump_(context, data):"},{"line_number":126,"context_line":"    return yaml.safe_dump(data, default_flow_style\u003dFalse)"},{"line_number":127,"context_line":""},{"line_number":128,"context_line":""}],"source_content_type":"text/x-python","patch_set":1,"id":"3f4b6375_0ca226af","line":125,"in_reply_to":"3f4b6375_2dd3ae62","updated":"2017-10-23 14:49:59.000000000","message":"I have no idea why we have data or context. I guess it was added as a quick/easy way to debug and output the context but I have never had a need for it.","commit_id":"8a0733b9d682de3cf67440bc4c58d60fb1e11356"},{"author":{"_account_id":8731,"name":"Renat Akhmerov","email":"renat.akhmerov@gmail.com","username":"rakhmerov"},"change_message_id":"b4e3c9ff62e47fa91ae3af70710eb8114dbf2415","unresolved":false,"context_lines":[{"line_number":122,"context_line":"    ).replace(\"\\\\n\", \"\\n\").replace(\" \\n\", \"\\n\")"},{"line_number":123,"context_line":""},{"line_number":124,"context_line":""},{"line_number":125,"context_line":"def yaml_dump_(context, data):"},{"line_number":126,"context_line":"    return yaml.safe_dump(data, default_flow_style\u003dFalse)"},{"line_number":127,"context_line":""},{"line_number":128,"context_line":""}],"source_content_type":"text/x-python","patch_set":1,"id":"3f4b6375_2dd3ae62","line":125,"in_reply_to":"3f4b6375_7214084f","updated":"2017-10-23 04:21:24.000000000","message":"On the context thing. I actually don\u0027t understand why we do \"data or context\". Do you have any explanation of that? So basically we return either jsonyfied data or context. Seems really strange. I would probably remove \"context\" from this expression and add a check for \"data\" being None.\n\nOn renaming.. We can safely rename it in the code, np problem. And in order to keep backwards compatibility we can just add one more alias \"json_dump\" in setup.cfg. We can also make \"json_pp\" deprecated, just by adding a comment in setup.cfg against it. How about that?","commit_id":"8a0733b9d682de3cf67440bc4c58d60fb1e11356"}]}
