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.

Sign up for GitHub

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

Jump to bottom

Rename Field refactoring allows the use of declared method names as new field names #763

Closed
Tracked by #779
researcher175 opened this issue Feb 27, 2024 · 1 comment
Closed
Tracked by #779

Rename Field refactoring allows the use of declared method names as new field names #763

researcher175 opened this issue Feb 27, 2024 · 1 comment
Labels
enhancement rename-refactor rename-target

Comments

@researcher175
Copy link

Rename Field refactoring allows the use of declared method names as new field names
It would be nice if Rope emits an alert to the user and asks if want to continue the application, avoiding incompatible types

Steps to reproduce the behavior:

  1. Code before refactoring:
string_types = (str,)


def with_metaclass():
    pass
  1. Apply the Rename Field refactoring using 'with_metaclass' as the new name for 'string_types'.
@researcher175 researcher175 added the bug Unexpected or incorrect user-visible behavior label Feb 27, 2024
@lieryan lieryan mentioned this issue Mar 12, 2024
Open
8 tasks
@lieryan
Copy link
Member

lieryan commented Mar 12, 2024

Closing. Ticket merged into #779.

@lieryan lieryan closed this as not planned Won't fix, can't repro, duplicate, stale Mar 12, 2024
@lieryan lieryan added enhancement and removed bug Unexpected or incorrect user-visible behavior labels Mar 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement rename-refactor rename-target
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lieryan @researcher175