-
Notifications
You must be signed in to change notification settings - Fork 1.4k
add-target
breaks resulting package when target name is not valid Swift identifier
#7764
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.
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
Merged
DougGregor
merged 6 commits into
swiftlang:main
from
dmhts:dmhts/fix-add-target-with-name-as-invalid-identifier
Aug 25, 2024
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
9e15797
Use "Example" prefix instead of actual target name
dmhts e515806
Merge remote-tracking branch 'upstream/main' into dmhts/fix-add-targe…
dmhts 627b625
Introduce target name sanitized name
dmhts 88ffe20
Use uppercase characters and spaces in tests
dmhts 3160ed5
Use localized capitalizing
dmhts d8d4e3f
Merge remote-tracking branch 'upstream/main' into dmhts/fix-add-targe…
dmhts File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -468,7 +468,7 @@ class ManifestEditTests: XCTestCase { | |
// These are the targets | ||
.target(name: "MyLib"), | ||
.executableTarget( | ||
name: "MyProgram", | ||
name: "MyProgram target-name", | ||
dependencies: [ | ||
.product(name: "SwiftSyntax", package: "swift-syntax"), | ||
.target(name: "TargetLib"), | ||
|
@@ -479,13 +479,13 @@ class ManifestEditTests: XCTestCase { | |
) | ||
""", | ||
expectedAuxiliarySources: [ | ||
RelativePath("Sources/MyProgram/MyProgram.swift") : """ | ||
RelativePath("Sources/MyProgram target-name/MyProgram target-name.swift") : """ | ||
import MyLib | ||
import SwiftSyntax | ||
import TargetLib | ||
|
||
@main | ||
struct MyProgramMain { | ||
struct MyProgram_target_nameMain { | ||
static func main() { | ||
print("Hello, world") | ||
} | ||
|
@@ -494,7 +494,7 @@ class ManifestEditTests: XCTestCase { | |
]) { manifest in | ||
try AddTarget.addTarget( | ||
TargetDescription( | ||
name: "MyProgram", | ||
name: "MyProgram target-name", | ||
dependencies: [ | ||
.product(name: "SwiftSyntax", package: "swift-syntax"), | ||
.target(name: "TargetLib", condition: nil), | ||
|
@@ -528,7 +528,7 @@ class ManifestEditTests: XCTestCase { | |
], | ||
targets: [ | ||
.macro( | ||
name: "MyMacro", | ||
name: "MyMacro target-name", | ||
dependencies: [ | ||
.product(name: "SwiftCompilerPlugin", package: "swift-syntax"), | ||
.product(name: "SwiftSyntaxMacros", package: "swift-syntax") | ||
|
@@ -538,33 +538,33 @@ class ManifestEditTests: XCTestCase { | |
) | ||
""", | ||
expectedAuxiliarySources: [ | ||
RelativePath("Sources/MyMacro/MyMacro.swift") : """ | ||
RelativePath("Sources/MyMacro target-name/MyMacro target-name.swift") : """ | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Though spaces work for file names, we could consider sanitizing them too. |
||
import SwiftCompilerPlugin | ||
import SwiftSyntaxMacros | ||
|
||
struct MyMacro: Macro { | ||
struct MyMacro_target_name: Macro { | ||
/// TODO: Implement one or more of the protocols that inherit | ||
/// from Macro. The appropriate macro protocol is determined | ||
/// by the "macro" declaration that MyMacro implements. | ||
/// by the "macro" declaration that MyMacro_target_name implements. | ||
/// Examples include: | ||
/// @freestanding(expression) macro --> ExpressionMacro | ||
/// @attached(member) macro --> MemberMacro | ||
} | ||
""", | ||
RelativePath("Sources/MyMacro/ProvidedMacros.swift") : """ | ||
RelativePath("Sources/MyMacro target-name/ProvidedMacros.swift") : """ | ||
import SwiftCompilerPlugin | ||
|
||
@main | ||
struct MyMacroMacros: CompilerPlugin { | ||
struct MyMacro_target_nameMacros: CompilerPlugin { | ||
let providingMacros: [Macro.Type] = [ | ||
MyMacro.self, | ||
MyMacro_target_name.self, | ||
] | ||
} | ||
""" | ||
] | ||
) { manifest in | ||
try AddTarget.addTarget( | ||
TargetDescription(name: "MyMacro", type: .macro), | ||
TargetDescription(name: "MyMacro target-name", type: .macro), | ||
to: manifest | ||
) | ||
} | ||
|
@@ -582,17 +582,17 @@ class ManifestEditTests: XCTestCase { | |
let package = Package( | ||
name: "packages", | ||
targets: [ | ||
.testTarget(name: "MyTest"), | ||
.testTarget(name: "MyTest target-name"), | ||
] | ||
) | ||
""", | ||
expectedAuxiliarySources: [ | ||
RelativePath("Tests/MyTest/MyTest.swift") : """ | ||
RelativePath("Tests/MyTest target-name/MyTest target-name.swift") : """ | ||
import Testing | ||
|
||
@Suite | ||
struct MyTestTests { | ||
@Test("MyTest tests") | ||
struct MyTest_target_nameTests { | ||
@Test("MyTest_target_name tests") | ||
func example() { | ||
#expect(42 == 17 + 25) | ||
} | ||
|
@@ -601,7 +601,7 @@ class ManifestEditTests: XCTestCase { | |
]) { manifest in | ||
try AddTarget.addTarget( | ||
TargetDescription( | ||
name: "MyTest", | ||
name: "MyTest target-name", | ||
type: .test | ||
), | ||
to: manifest, | ||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about using
c99name
instead?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's a very good point.
c99name
would certainly cover most edge cases, such as using dash-case, special characters, and digits in the first character. Well, it's already used for language-level target name sanitizing so it must be robust enough for this use case.The only remaining concern is that
c99
(obviously) doesn't cover Swift's reserved words. However, in that case, we could "just" escape the reserved word based on a list taken e.g. from swift-syntax, whichSwiftPM
already depends on.I believe combining these two safeguards should be a good enough way to proceed. What do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm just visiting. :) There may be a better way to avoid reserved names—the package owners probably have ideas!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alright :) @DougGregor, maybe you have some ideas about this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Both of your ideas together (
cc9name
and using the swift-syntax keyword checking) sound reasonable to me.