Xcode should offer a fixit for ensuring private modules have canonical names

Originator:matej
Number:rdar://40829112 Date Originated:05-Jun-2018 04:42 PM
Status:Open Resolved:
Product:Developer Tools Product Version:Xcode Version 10.0 beta (10L176w)
Classification:Enhancement Reproducible:Always
 
Summary:
Xcode presents the following warnings, if a private module does not have a canonical name: “expected canonical name for private module”. The error does not specify how exactly the issue can be resolved (by using a `_`). It would be easy to offer a fix that does this automatically. 

Steps to Reproduce:
Use a non-canonical private module name, like PSPDFKitPrivate. Xcode outputs a warning but does not offer a fixit. 

Expected Results:
There should be a fixit available. This should already be supported by the compiler. 

Actual Results:
Example warnings:

/Users/matej/Library/Developer/Xcode/DerivedData/Viewer-fjfffqfhjcndpmcoftyeyquudvor/Build/Products/Debug-iphonesimulator/PSPDFKitUI.framework/Modules/module.private.modulemap:1:18: note: rename 'PSPDFKitUIPrivate' to ensure it can be found by name
framework module PSPDFKitUIPrivate {
                 ^
/Users/matej/Library/Developer/Xcode/DerivedData/Viewer-fjfffqfhjcndpmcoftyeyquudvor/Build/Products/Debug-iphonesimulator/PSPDFKit.framework/Modules/module.private.modulemap:1:18: warning: expected canonical name for private module 'PSPDFKitPrivate'
framework module PSPDFKitPrivate {

Version:
Xcode Version 10.0 beta (10L176w)

Notes:
This was discussed in WWDC labs 2018.

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!