Fix changing keys of data providers for tests with optional arguments - #783
Merged
TomasVotruba merged 1 commit intoSep 17, 2026
Conversation
tunterreitmeier
force-pushed
the
fix-optional-named-arguments-data-provider
branch
from
September 17, 2026 06:39
9a3deed to
5d41dc9
Compare
Member
|
LGTM, Thank you 👍 |
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
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.
Hi, I noticed that the
NamedArgumentForDataProviderRectorcurrently tries to fix named arguments, even when every key matches an argument. This can break tests, when there are optional arguments involved.So when running the rule on this example
one would end up with this diff:
My proposed fix would be to skip if all the keys are already all named arguments, using
array_diff.Hope that helps. Thanks a lot!