-
-
Notifications
You must be signed in to change notification settings - Fork 964
Automatic validation may cause issues with fields that are generated #1211
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
Comments
Kocal
added a commit
to Kocal/symfony-app-template
that referenced
this issue
Aug 3, 2019
Kocal
added a commit
to Kocal/symfony-app-template
that referenced
this issue
Aug 3, 2019
I think this one can be closed, isn’t it ? |
Why? |
I thougth that #1211 resolves the problem but it’s a « small » fix and we are looking for a better solution ? |
For everyone that comes here and is looking to disable auto validation: just comment out the following lines:
in config/packages/validator.yaml |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Say you have an entity with a
createdAt
/updatedAt
field that is automatically filled. When creating a request, you may have a400
error because these fields can not be empty/null.The solution is to disable automatic validation for now?
This was working before the update of the validator recipe: symfony/recipes#559
Feature PR initiating the feature: symfony/symfony#27735
Disabling auto mapping: symfony/recipes#612
Related issue: symfony/symfony#32070 (comment)
Thanks @Kocal for the bug report. I'm not sure if the end solution is to document this behavior or fix it upstream (in symfony) @dunglas ?
The text was updated successfully, but these errors were encountered: