On 12/17/2015 11:45 PM, Stephan Beal wrote:
On Thu, Dec 17, 2015 at 9:28 PM, Ross Berteig <r...@cheshireeng.com <mailto:r...@cheshireeng.com>> wrote:Build fossil with JSON support, then you get access to a bunch of features with data transported in JSON with suitable quoting. I'm not sure why JSON is not enabled in the official distributions, it works for me. It's historical: Richard said, way back when, that he'd enable it if it got full-featured testing, including fuzzy input tests (to check against external exploits using invalid inputs). i never did that, and my ongoing arm nerve damage (from too much/sustained typing!) is keeping me from meaningfully contributing to any software for the foreseeable future, so i'm not likely to ever get around to it :/. Contributions would be welcomed!
I really should sign and mail that contributor agreement.... perhaps this is as good a reason as any. Then I can probably find some time to attack test cases for JSON, and maybe with you nagging^H^H^H^H^H^Hmentoring me it could become an official feature.
I swiftly realized that while the existing "fossil ticket" commands allowed for easy access to summary reports, there was no good way to get the full body of a ticket and its commentary out in a way that could be used for automating their publication. I needed that, and you added JSON at exactly the moment I was looking for it.
-- Ross Berteig r...@cheshireeng.com Cheshire Engineering Corp. http://www.CheshireEng.com/ +1 626 303 1602 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
