Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Namespace all remaining files in includes/exception | James D. Forrester | 2025-03-25 | 1 | -1/+1 |
| | | | | | | | | | In MediaWiki/Exception, to follow PSR-4 per plural vs. singular (this can be changed later if people really care). Also, move the couple of exceptions in here that were already namespaced in the MW-top-level into the new space. Bug: T353458 Change-Id: I12ed850ae99effb699a6d7ada173f54e72f0570e | ||||
* | Rest: Handle exceptions during handler creation | Gergő Tisza | 2023-01-22 | 3 | -6/+6 |
| | | | | Change-Id: Ia5e31a875161a07b0d4de7ae0eaf6e78e6e86a27 | ||||
* | REST: gracefully handle all exceptions. | daniel | 2021-11-02 | 3 | -0/+88 |
ResponseFactory::createFromException already had support for arbitrary exceptions, but Router was so far only using it for HttpExceptions, leaving other kinds of exceptions uncaught. In addition to catching all exceptions and generating an appropriate JSON response for them, this patch introduces the ErrorReporter interface, with an MWErrorReporter implementation which calls MWExceptionHandler::rollbackMasterChangesAndLog(). This is how uncaught errors are handled for requests coming in via api.php, so it seems appropriate to use the same approach for requests coming in via rest.php. Bug: T285984 Change-Id: I0605a7693821ef58fac80ab67f51a742556a37fd |