|
12 | 12 | namespace Symfony\Component\Routing\Generator;
|
13 | 13 |
|
14 | 14 | /**
|
15 |
| - * ConfigurableRequirementsInterface must be implemented by URL generators in order |
16 |
| - * to be able to configure whether an exception should be generated when the |
17 |
| - * parameters do not match the requirements. |
| 15 | + * ConfigurableRequirementsInterface must be implemented by URL generators that |
| 16 | + * can be configured whether an exception should be generated when the parameters |
| 17 | + * do not match the requirements. It is also possible to disable the requirements |
| 18 | + * check for URL generation completely. |
| 19 | + * |
| 20 | + * The possible configurations and use-cases: |
| 21 | + * - setStrictRequirements(true): Throw an exception for mismatching requirements. This |
| 22 | + * is mostly useful in development environment. |
| 23 | + * - setStrictRequirements(false): Don't throw an exception but return null as URL for |
| 24 | + * mismatching requirements and log the problem. Useful when you cannot control all |
| 25 | + * params because they come from third party libs but don't want to have a 404 in |
| 26 | + * production environment. It should log the mismatch so one can review it. |
| 27 | + * - setStrictRequirements(null): Return the URL with the given parameters without |
| 28 | + * checking the requirements at all. When generating an URL you should either trust |
| 29 | + * your params or you validated them beforehand because otherwise it would break your |
| 30 | + * link anyway. So in production environment you should know that params always pass |
| 31 | + * the requirements. Thus this option allows to disable the check on URL generation for |
| 32 | + * performance reasons (saving a preg_match for each requirement every time a URL is |
| 33 | + * generated). |
18 | 34 | *
|
19 | 35 | * @author Fabien Potencier <fabien@symfony.com>
|
| 36 | + * @author Tobias Schultze <http://tobion.de> |
20 | 37 | */
|
21 | 38 | interface ConfigurableRequirementsInterface
|
22 | 39 | {
|
23 | 40 | /**
|
24 | 41 | * Enables or disables the exception on incorrect parameters.
|
| 42 | + * Passing null will deactivate the requirements check completely. |
25 | 43 | *
|
26 |
| - * @param Boolean $enabled |
| 44 | + * @param Boolean|null $enabled |
27 | 45 | */
|
28 | 46 | public function setStrictRequirements($enabled);
|
29 | 47 |
|
30 | 48 | /**
|
31 |
| - * Gets the strict check of incorrect parameters. |
| 49 | + * Returns whether to throw an exception on incorrect parameters. |
| 50 | + * Null means the requirements check is deactivated completely. |
32 | 51 | *
|
33 |
| - * @return Boolean |
| 52 | + * @return Boolean|null |
34 | 53 | */
|
35 | 54 | public function isStrictRequirements();
|
36 | 55 | }
|
0 commit comments