I'll take a look 🫡

what's the problem actually? Xcode will produce strings or stringsdict automatically if we put a xcstrings.

Hey @muukii 👋🏼
Are you sure about that? I have never used strings catalogs, but after a quick test on ios_app_with_frameworks_and_resources I see that whenever I migrate .stringsto a strings catalog, it doesn’t exist in a project anymore.
I think the point of this issue is to include strings catalog file in a generated workspace, because now it’s not included after generation.
However, swiftgen does not support strings catalog yet according to this issue. What should we do about it?

In my case, using different name to Localizable because I still have classic style strings file.
Specify table name as StringCatalog to load. Not sure it's making some effects.

Yes, that's the possible solution, but in the context of tuist capabilities, it looks a bit like a workaround to hold both of these. I think

Just out of curiosity, are StringCatalog.strings and StringCatalog.xcstrings update each other, or if you want to add a new key, you need add it in both files?

A little update on this one.

As I mentioned before SwiftGen does not support .xcstrings files yet.
I've tried to implement the solution mentioned here, however, flow .xcstrings -> .strings -> .swift does not fit into current resource synthesizer generator, because it requires running it twice. In addition, it doesn't support plurals(.stringsdict)

IMHO best solution would be to write custom .stencil supporting .xcstrings files in SwiftGen, and then extend TuistGenerator with a .xcstrings support. I can start to work on it, but I'm not an expert in writing stencils(yet 🤞)

IMHO best solution would be to write custom .stencil supporting .xcstrings files in SwiftGen, and then extend TuistGenerator with a .xcstrings support. I can start to work on it, but I'm not an expert in writing stencils(yet 🤞)

@leszko11 is there any way we can support you in making this happen?

@pepicrft It's in progress. I know it's going slow, but so far I've implemented all the setup required to generate .swift file from .xcstring and started to write a stencil template. I'm trying to be as close as possible to the strings asset file generated from .strings.
Aiming to complete it end of this week

Amazing, thanks for the update 🙌 Let us know if you need anything from us 🙂 Happy to take a look at some early draft if you want to align on the direction of the PR

I'm stuck 😔

.xcstring file under the hood is a .json file, so it needs swiftgen's JSON parser to process the file. Not using strings parser means that we're losing an access to a types property which holds a list of arguments used in translation. Without it, I have no clue, how to do it.

I've found this tool, which basically uses a strings parser to process .xcstring file and produce synthesised resources

@leszko11 it seems that you'll have to contribute a new parser to SwiftGen that might reuse logic from the parsers that you mentioned (the JSON and the Strings). I'm not entirely familiar with the SwiftGen codebase, but it seems that those parsers can be of good reference.

@pepicrft Yep, I think that would be the best solution. I'll start a conversation in corresponding issue

SwiftGen/SwiftGen#1124

👀

Niiiice! SwiftGen users will be very excited about that contribution. Thanks for making it happen @leszko11

Commenting to stay informed about this topic.
Can't wait to migrate to string catalogs when youre done and it's available in a new tuist version! 🎉

Greetings