Jumping to Swift Interface of my own headers is disruptive and annoying.
| Originator: | bjhomer | ||
| Number: | rdar://28339128 | Date Originated: | 16-Sep-2016 |
| Status: | Open | Resolved: | |
| Product: | Xcode | Product Version: | 8.0 |
| Classification: | UI/Usability | Reproducible: | Always |
BJ Homer16-Sep-2016 11:04 AM Summary: If I am looking at a Swift source file and Open Quickly to jump to an Objective-C header, I instead get the generated Swift interface. That's rarely what I wanted; if I'm navigating to my own header, I'm likely to want to modify it. And once I'm on the generated header, I have to use a menu item to get back to the original source. It's useful to be able to see the generated Swift interface for an Objective-C type, but it's disruptive and annoying for Xcode to jump to it by default. If I chose to navigate to a `.h` file, please open the actual .h file. Steps to Reproduce: 1. Add a Swift file and an Objective-C header file to a project. 2. Open the Swift file in the editor. 3. Use "Open Quickly" to navigate to the Objective-C header file. Expected Results: The header file should appear in the editor. Actual Results: The Swift generated interface appears in the editor. And because it's just generated content, I can't edit it. Version: Xcode 8.0 (8A218a) macOS Sierra GM (16A320) Notes: There seems to be an assumption that navigating from a Swift file to an Objective-C header is primarily done in order to inspect the existing interface. In my experience, it's *more* likely that I want to edit the header file in order to add a method or improve how the existing interface is presented in Swift. An assumption of non-editability is not justified. Configuration: Attachments:
Comments
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!