JSON is quite widely used serialisation format, it would be good to have support for export/import it.
Discussion
Anonymous
-
2010-07-28
So, admittedly, this is the first time I do anything actively here on sf, so sorry for any inconvenience I cause.
I had the need for JSON (export) support quiet recently, so I decided to fork the php_array export code and turned it into simple a simple exporter for JSON.
So, obviously I can't attach a file or something like that, so I decided to just pastebin my result... In hope that it helps.
Yes, SourceForge doesn't make it easy to attach a file -- what you would have had to do is create a new Patches tracker item, attach it there, and reference that tracker artifact ID or URL here.
So, admittedly, this is the first time I do anything actively here on sf, so sorry for any inconvenience I cause.
I had the need for JSON (export) support quiet recently, so I decided to fork the php_array export code and turned it into simple a simple exporter for JSON.
So, obviously I can't attach a file or something like that, so I decided to just pastebin my result... In hope that it helps.
http://pastebin.com/sfUccTq2
Yes, SourceForge doesn't make it easy to attach a file -- what you would have had to do is create a new Patches tracker item, attach it there, and reference that tracker artifact ID or URL here.
Since pastebin posts often expire, I hope you don't mind that I did just that -- the patch is at https://sourceforge.net/tracker/?func=detail&aid=3038312&group_id=23067&atid=377410
Export patch merged for 3.4. I removed the author name per out policy; also changed generated file to .json.
As the patch is merged, I assume this can be closed.
Can we add feature to IMPORT a .JSON file?