Produce warnings when a Strings Catalog phrases are ignored by the tool
liamnichols opened this issue · comments
There are two scenarios where we ignore strings in a catalog:
- A value is missing in the source language
- This is common if the key is the phrase
- The key is automatically managed
- This happens when the compiler is syncing the key from Swift source code
We have to ignore these keys because it means that they typically haven't been properly defined by the developer can't cant be represented in Swift, but ignoring them with no warning can leave the developer confused and frustrated when the Swift property cannot be found.
I've even confused myself about this a couple of time during development.
Because XCStrings Tool has strong opinions on using manually created strings with a key and default value, we should produce a warning that can help surface this misconfiguration and guide the developer to correct it.