Prevent symbol conflicts when using `accessLevel: public` across multiple packages

[markst]

Describe the problem

When using XCStringsToolPlugin across multiple Swift packages, setting accessLevel: public in just one package's xcstrings-tool-config.yml causes a conflict if other packages also generate a Localizable symbol (even with default internal access level).

The compiler reports:

'Localizable' is ambiguous for type lookup in this context

This happens because one module exports Localizable publicly, while others still generate the same symbol internally — leading to ambiguity when multiple modules are imported into the same target.

Steps to Reproduce

1. Add .xcstrings files to two Swift packages: PackageA and PackageB
2. Set accessLevel: public in PackageA’s config only
3. Leave PackageB with default or internal
4. Import both packages into an app target
5. Use Localizable.someString

[liamnichols]

Thanks for flagging this @markst, although i'm not really sure what we can do here 🤔 It mostly comes down to limitations with the Swift type system. I think you might be able to use an explicit module name to disambiguate though?

While I don't think you can reference PackageB.String.Localizable directly, you might be able to define a typealias in PackageB` like so:

public typealias PackageBLocalizable = String.Localizable
// or 
public typealias Localizable = String.Localizable

Then reference PackageBLocalizable or PackageB.Localizable in your app target instead?

Does that work the way you need it to?

Alternatively, you can just rename the .xcstrings file to something other than Localizable I guess.

Or did you have something in mind that we could do with the generated code to avoid this?