ExtractionState config about xcstrings-tool HOT 3 OPEN

Thanks for reporting this! This is an interesting issue 🤔 It seems that Xcode will consider a string with a missing extractionState as automatically managed:

The reason that we skip/warn about Automatically managed strings is that there is potential for Xcode to see the generated definition try to update the source in the Strings Catalogs (essentially overwriting what you have defined) which is something that we want to avoid.

Before going down the route of overriding this, could you confirm if you have spoken with your translation platform about this? I would expect that the value should be either preserved from upload, or set to manual if your generating a Strings Catalog from phrases that are defined in the platform directly.

As a temporary workaround, you could use jq to post-process the file after downloading:

jq --indent 2 '.strings |= map_values(if has("extractionState") then . else {"extractionState": "manual"} + . end)' Localizable.xcstrings > Localizable.xcstrings.tmp && mv Localizable.xcstrings.tmp Localizable.xcstrings

from xcstrings-tool.

Thanks for workaround.
I have already contacted team of online tool, to set this field to manual or provide option to configure it.

However, there might be others edge cases with this field.
I believe this should be an easy fix on tool side. For example some static variable (array?) with StringExtractionState value to ignore/warning probably?

from xcstrings-tool.

It's relatively easy to add configuration options to the CLI, but there isn't really a good way to pass flags through when using the Package Plugin (I don't encourage the usage of the CLI directly atm).

I'm interested to see which other scenarios where the extractionState is set to something other than manual or automatic to understand if the customisation would be the appropriate way to handle it or not

from xcstrings-tool.