[DomCrawler] Don't return file infos for empty file fields#59621
[DomCrawler] Don't return file infos for empty file fields#59621rudiedirkx wants to merge 3 commits into
Conversation
|
Hey! I see that this is your first PR. That is great! Welcome! Symfony has a contribution guide which I suggest you to read. In short:
Review the GitHub status checks of your pull request and try to solve the reported issues. If some tests are failing, try to see if they are failing because of this change. When two Symfony core team members approve this change, it will be merged and you will become an official Symfony contributor! I am going to sit back now and wait for the reviews. Cheers! Carsonbot |
|
Let me close as that cannot be the correct solution. The changes in the test cases highlight how this might break existing apps. |
…nicolas-grekas) This PR was merged into the 6.4 branch. Discussion ---------- [BrowserKit] Fix submitting forms with empty file fields | Q | A | ------------- | --- | Branch? | 6.4 | Bug fix? | yes | New feature? | no | Deprecations? | no | Issues | Fix #49014 | License | MIT Replaces #53586 and #59621 Commits ------- 0fbfc3e [BrowserKit] Fix submitting forms with empty file fields
Fixes #49014 but not in a meaningful way IMO. But I don't know where else to remove empty files. Could be in
Request(browser-kit), or even later inMultipartPart(mime). I don't understand why dom-crawler works this way, so I don't know how to fix it correctly.To do: fix tests..?