Joshua Spence a2f909f0bd Improve XHPAST handling of syntax errors ... Summary: Currently, a bunch of developers are using #xhpast for writing custom linter rules. As such, we end up with a fair few `XHPASTSyntaxErrorException` in our PHP error logs. I think that throwing an exception is not quite correct in this case because it is somewhat expected that invalid PHP may be entered. Instead, catch the exception and show the user a helpful message. Test Plan: This doesn't quite work yet... the stream and tree views render as blank but the exceptions still propogate to the error logs. Mostly, I'm not sure how the exception should be rendered for display. Reviewers: epriestley, #blessed_reviewers Reviewed By: epriestley, #blessed_reviewers Subscribers: Korvin Differential Revision: https://secure.phabricator.com/D14028		2015-11-09 07:03:32 +11:00
..
builtin	Make modular transforms handle exceptions gracefully	2015-05-13 11:38:45 -07:00
celerity	Add Can Create Policy Capability to Phame Blogs	2015-11-08 07:00:18 -08:00
chatbot	Remove PhabricatorBotDifferentialNotificationHandler reference in example_config.json for phabot	2014-06-11 09:36:30 -07:00
cows	Use PHP implementation of Cowsay for cowsay rule	2015-09-13 12:27:30 -07:00
figlet/custom	Include "Figlet" and PEAR "Text_Figlet" in externals	2015-09-13 12:30:48 -07:00
font	Made Meme Generator	2013-01-19 18:43:43 -08:00
sprite	Update Asana Logo	2015-09-30 10:15:53 -07:00
sql	Improve XHPAST handling of syntax errors	2015-11-09 07:03:32 +11:00
sshd	Update repository hosting documentation for all the issues users have hit	2014-03-26 06:44:18 -07:00