Add support to define location for all generated files #34
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.
This change required a bit more code changes that resulted in few bug fixes and potentially a few breaking changes in future .
Fixes:
plist.SomeFile.someKey##{one}
) it didn't work as expected, should be fixed now and corresponding stringsdict file will be createdTo still be able to maintain some backwards compatibility I renamed
Configuration
toConfigurationV1
and created newConfigurationV2
. V1 is convertible to V2 so if decoding V2 fails, I try to decode V1 and convert it. V2 removed few keys (strings(Dict)FileName
,destinationDir
) in favor of newdefaultFileName
anddestinations
keys. Asdestinations
dictionary requires at least single entry withdefaultFileName
key, I madedefaultFileName
required as it makes sense I think.The process of generating localizations is a bit different now, it used to be
From now on it is bit more generic:
The part with this generation is currently not well testable (#19) so no tests were added 😞 I only tested it on few of our projects.