2 commits

Author	SHA1	Message	Date
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
vrana	2cc7f82ece	Move Conduit methods inside applications ... Test Plan: /conduit/ /conduit/method/arcanist.projectinfo/ Call method $ echo '{}' | arc call-conduit user.whoami Reviewers: epriestley Reviewed By: epriestley CC: aran, Korvin Differential Revision: https://secure.phabricator.com/D4268	2012-12-21 12:21:59 -08:00

Renamed from src/applications/xhpastview/controller/PhabricatorXHPASTViewController.php (Browse further)