Skip to content

[DomCrawler] Don't return file infos for empty file fields #59621

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

Closed
wants to merge 3 commits into from

Conversation

rudiedirkx
Copy link

@rudiedirkx rudiedirkx commented Jan 26, 2025

Q A
Branch? 7.3
Bug fix? yes
New feature? no
Deprecations? no
Issues Fix #49014
License MIT

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 in MultipartPart (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..?

@carsonbot
Copy link

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:

  • Always add tests
  • Keep backward compatibility (see https://symfony.com/bc).
  • Bug fixes must be submitted against the lowest maintained branch where they apply (see https://symfony.com/releases)
  • Features and deprecations must be submitted against the 7.3 branch.

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!
If this PR is merged in a lower version branch, it will be merged up to all maintained branches within a few days.

I am going to sit back now and wait for the reviews.

Cheers!

Carsonbot

@OskarStark OskarStark changed the title [dom-crawler] Don't return file infos for empty file fields Don't return file infos for empty file fields Jan 27, 2025
@carsonbot carsonbot changed the title Don't return file infos for empty file fields [DomCrawler] Don't return file infos for empty file fields Jan 27, 2025
@nicolas-grekas
Copy link
Member

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 added a commit that referenced this pull request Feb 11, 2025
…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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

dom-crawler + browser-kit empty file upload error "Path cannot be empty"
4 participants