Refactoring the name of a class does not refactor typed collections

Originator:paulo.fierro
Number:rdar://23081877 Date Originated:12-Oct-2015 08:13 PM
Status:Closed Resolved:20-Oct-2015 11:55AM
Product:Developer Tools Product Version:Version 7.0.1 (7A1001)
Classification:Other Bug Reproducible:Always
 
Summary:
When using lightweight generics in Objective-C, refactoring the name of a class that is used as a type for collections does not update the class name in the collection declarations.

Steps to Reproduce:
1. Create a new class that inherits from NSObject, e.g. PFCustomObject
2. Define a property as a collection of that class, e.g. NSMutableArray <PFCustomObject *> *list;
3. Rename the name of the custom class via Edit > Refactor > Rename to something else, e.g. PFObject

Expected Results:

The class and filename are renamed as well as collections that reference it, e.g. “NSMutableArray <PFCustomObject *> *list” would become “NSMutableArray <PFObject *> *list”

Actual Results:

The class and filename are renamed but collections that reference it are not updated. So “NSMutableArray <PFCustomObject *> *list” is not modified.

Comments

Engineering has determined that your bug report (23081877) is a duplicate of another issue (19727373) and will be closed.

By paulo.fierro at Oct. 20, 2015, 4:56 p.m. (reply...)

Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!