Skip to content
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

Add failing test fixture for UnderscoreToCamelCaseLocalVariableNameRector #5748

Closed
wants to merge 1 commit into from
Closed

Conversation

sanmai
Copy link
Contributor

@sanmai sanmai commented Mar 3, 2021

Failing Test for UnderscoreToCamelCaseLocalVariableNameRector

Based on https://getrector.org/demo/754d498e-ac9d-4f72-9d8c-d695f340318b

Another addition to #5739 and #5715.

Shall we fix #5750 this once and for all, or shall I invent more cases?

@samsonasik
Copy link
Member

samsonasik commented Mar 3, 2021

Latest getrector.org may not up to date, so using getrector.org may not be accurate. Using failing test case like this is the way we can detect the bug.

I think one by one is ok as that will be easier to review. If you can provide a patch too, please do, thank you.

Base automatically changed from master to main March 11, 2021 19:15
@TomasVotruba
Copy link
Member

@samsonasik I tried to fix it, but it seems there is more than meets the eye. Could you look into this?
Service BreakingVariableRenameGuard might help, but it also report few false positives.

@samsonasik
Copy link
Member

@TomasVotruba yes, I tried as well, and it is very complex. I will try re-check on BreakingVariableRenameGuard

@TomasVotruba
Copy link
Member

See #5750 (comment)

TomasVotruba added a commit that referenced this pull request Mar 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Incorrect behavior of UnderscoreToCamelCaseLocalVariableNameRector
3 participants