Added part about serialization issues when using file-upload in non-API context #2160
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
PaddyS
changed the title
Added part about serialization when using a file upload with the User entity, which gets serialized by Symfony for the session.
|
Indeed this looks like it should be in Symfony's documentation, what do you think? |
|
Yeah, unfortunately I did not find a fitting Symfony documentation that actually takes care of VichUploaderBundle, besides mentioning it in a sidenote. I could imagine it here otherwise, in VichUploaderBundle's own documentation, maybe here: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added part about serialization when using a file upload with the User entity, which gets serialized by Symfony for the session.
Ignoring this will result in an PHP exception when trying to upload a file to the User entity via the Symfony form builder.
To be fair, this is not exactly an API platform issue, since the upload via API works flawlessly even without this change.
I just happened to face this issue in this context, and found several other public posts about people using API platform facing the same issue.
It's totally fine if you don't want to have that part in your documentation though!