Rename refactoring should check whether the target variable exists

未關閉
#779 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 7 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
22/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
停滯
技術堆疊
python
領域
tooling

研究方向

This is a tracking issue for several rename bugs in rope, a Python refactoring library, and it does not name a file or test. Start by reading the linked tickets (#776, #769, #768, #766, #765, #764, #763, #761) to find the concrete rename cases, then reproduce one of them against rope's rename refactoring. Done means a rename whose target name is already taken is rejected with a clear error, and the listed cases are verified against that change.

由索引模型根據 Issue 內容生成。

描述

enhancement rename-refactor

The following series of tickets all have the same root cause, rope currently doesn't validate whether the target variable name is currently occupied by another existing variable:

  • #776
  • #769
  • #768
  • #766
  • #765
  • #764
  • #763
  • #761

Collecting here into one big ticket since most of them will likely be resolved by the same solution.

Once this ticket is resolved, we'll go through each ticket to verify that those cases are addressed by the solution.

主要語言
Python
星號
2.2k
分支
197
平均合併
2 天 13 小時
30 天內合併 PR
5

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

python-rope/rope 的其他 Issue

查看 python-rope/rope 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。