ConfigurableRequirementsInterface must be implemented by URL generators that can be configured whether an exception should be generated when the parameters do not match the requirements. It is also possible to disable the requirements check for URL generation completely.
The possible configurations and use-cases:
@author Fabien Potencier <fabien@symfony.com> @author Tobias Schultze <http://tobion.de>
Expanded class hierarchy of ConfigurableRequirementsInterface
All classes that implement ConfigurableRequirementsInterface
interface ConfigurableRequirementsInterface {
/**
* Enables or disables the exception on incorrect parameters.
* Passing null will deactivate the requirements check completely.
*
* @param Boolean|null $enabled
*/
public function setStrictRequirements($enabled);
/**
* Returns whether to throw an exception on incorrect parameters.
* Null means the requirements check is deactivated completely.
*
* @return Boolean|null
*/
public function isStrictRequirements();
}
Name | Modifiers | Type | Description | Overrides |
---|---|---|---|---|
ConfigurableRequirementsInterface:: |
public | function | Returns whether to throw an exception on incorrect parameters. Null means the requirements check is deactivated completely. | 1 |
ConfigurableRequirementsInterface:: |
public | function | Enables or disables the exception on incorrect parameters. Passing null will deactivate the requirements check completely. | 1 |