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
Fix #565 #792
Fix #565 #792
Conversation
👍 |
Sorry, can you give feedback to this? |
Could you please squash your commits? thank you |
Change PUT by PATCH Refactor tests for nelmio#565
Done! |
thank you! |
👍 |
😍 |
Are you in the correct version? I've tested and worked fine |
I'm in 2.11 and I can see your edit in my vendors. |
It's strange, be sure to delete cache, etc. |
Already did. The input parameter is set to a form type, is it working with form types too? |
Maybe, the form fields have priority |
That's it. If I use the entity as the input parameter all the fields requirement are set to false. But it's not possible with a FormType then? |
I think also it should be well. |
So what am I missing here? Do you have to set all my form's fields to required => false? |
No, I think being a PATCH should ignore the form and put all |
So a new PR is needed right? |
Yeah, it's a new issue/PR |
Fix #565
Required fields will be false for
PATCH
routes instead ofPUT