You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, to use the validator component within a Symfony application, we need to configure the validation constraints as annotations or in XML or Yaml files in the Resources/config/validation directory or in a big Resources/config/validation.[x|y]ml file in a bundle directory.
In order to be able to re-use validation across libraries or just make the validation living where the user wants, I propose to introduce a validation mapping configuration in the framework configuration:
The mapping values can be either a directory or a file. If it's a file, will be added as YML or XML based on the extension. If it's a directory, then using the finder we will be able to locate all the *.[x|y]ml files.
Before PR this feature, what do you think about it ?
The text was updated successfully, but these errors were encountered:
Right now, to use the validator component within a Symfony application, we need to configure the validation constraints as annotations or in XML or Yaml files in the
Resources/config/validation
directory or in a bigResources/config/validation.[x|y]ml
file in a bundle directory.In order to be able to re-use validation across libraries or just make the validation living where the user wants, I propose to introduce a validation mapping configuration in the
framework
configuration:The mapping values can be either a directory or a file. If it's a file, will be added as YML or XML based on the extension. If it's a directory, then using the finder we will be able to locate all the
*.[x|y]ml
files.Before PR this feature, what do you think about it ?
The text was updated successfully, but these errors were encountered: