@@ -206,7 +206,7 @@ |
||
| 206 | 206 | $result = null; |
| 207 | 207 | } |
| 208 | 208 | } |
| 209 | - catch(Exception $e) { |
|
| 209 | + catch (Exception $e) { |
|
| 210 | 210 | // I don't care what happened personally; we'll just not bother |
| 211 | 211 | // overriding our existing dates. However, whatever called us |
| 212 | 212 | // might want to log this, as someone may be probing the app for |
@@ -205,8 +205,7 @@ |
||
| 205 | 205 | // Improbable dates could cause problems if used in DB queries. |
| 206 | 206 | $result = null; |
| 207 | 207 | } |
| 208 | - } |
|
| 209 | - catch(Exception $e) { |
|
| 208 | + } catch(Exception $e) { |
|
| 210 | 209 | // I don't care what happened personally; we'll just not bother |
| 211 | 210 | // overriding our existing dates. However, whatever called us |
| 212 | 211 | // might want to log this, as someone may be probing the app for |
@@ -66,8 +66,7 @@ |
||
| 66 | 66 | $filterData->overrideRatingFromUrlParam($request->query->getInt('rating', -1)); |
| 67 | 67 | $filterData->overrideStartDateFromUrlParam((string) $request->query->get('periodStartDate')); |
| 68 | 68 | $filterData->overrideEndDateFromUrlParam((string) $request->query->get('periodEndDate')); |
| 69 | - } |
|
| 70 | - catch (Exception $e) { |
|
| 69 | + } catch (Exception $e) { |
|
| 71 | 70 | // Someone may be trying to fiddle with our URL parameters. Don't fail; the override |
| 72 | 71 | // functions are sensible enough to ignore invalid inputs. But we should log. |
| 73 | 72 | $logger->error( |