-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[DomCrawler] No more exception on field name with strange format #18570
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
Conversation
Tests are failing, but if this PR can be accepted I will need some help to manage all the tests about malformed name... |
} | ||
} | ||
|
||
return $segments; | ||
} | ||
|
||
throw new \InvalidArgumentException(sprintf('Malformed field path "%s"', $name)); | ||
return [$name]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should be array($name)
this cannot be accepted without tests covering these cases to prevent regressions |
I think that the things I will do is to remove the tests that check if the DomCrawler raise error when the name is malformed. |
@guiled remove these tests & move the used-to-be invalid names to a test ensuring they now are accepted :) |
@guiled do you have time to finish this PR? |
I'm taking over to finish this one. See #19138 |
…format (guiled, fabpot) This PR was merged into the 2.7 branch. Discussion ---------- [DomCrawler] No more exception on field name with strange format | Q | A | ------------- | --- | Branch? | 2.7 | Bug fix? | yes | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | #18569, #18570 | License | MIT | Doc PR | n/a Commits ------- e204913 finished previous commit 953a383 No more exception for malformed input name
Uh oh!
There was an error while loading. Please reload this page.