Provide LOCALIZED_STRING_CODE_COMMENTS build setting definition #984
Conversation
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
Clients of SwiftBuild can use this to inform String Catalog sync and other localization behaviors.
matthewseaman
requested review from
aciidgh,
jakepetroules,
mhrawdon,
neonichu and
owenv
as code owners
Contributor
Author
|
@swift-ci test |
Tantalum73
approved these changes
Dec 16, 2025
owenv
approved these changes
Dec 16, 2025
Contributor
Author
|
@swift-ci test macOS |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Adding cousin setting to
LOCALIZED_STRING_MACRO_NAMESandLOCALIZED_STRING_SWIFTUI_SUPPORTto specify whether extracting strings from code comments is desirable. By default it is not.Like the similar settings, clients of SwiftBuild can use this to inform String Catalog sync and other localization behaviors.
The use case for setting this to YES is for projects that previously relied on this documented feature of
genstringsin order to specify strings in a source file that would otherwise be dynamically constructed in code.