-
Notifications
You must be signed in to change notification settings - Fork 6
[DIT-11970] iOS Strings Format Support #129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DIT-11970] iOS Strings Format Support #129
Conversation
…class, and IOSStringsOutput file
…riants and projects as expected. Moved shared BaseFormatter class methods out of JSON and IOSStringsFormatters
lib/src/formatters/iosStrings.ts
Outdated
| const components = await this.fetchComponents(); | ||
| const variables = await this.fetchVariables(); | ||
|
|
||
| const variablesById = variables.reduce((acc, variable) => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we use this anywhere? I see we have a variable output file but am not seeing how that gets populated. In the base class maybe?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah good question, the variables are a big ? for me too. Gonna dig into those now and will report back
…ponent mapping to iosStringsFormatter
… Unit tests additions to IOSStringsFormatter class
| * | ||
| * @returns {OutputFile[]} List of Output Files | ||
| */ | ||
| protected transformAPIData(data: IOSStringsAPIData) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A little weird to call these "formatters" now that the export endpoint will do all of the formatting and all this is doing is saving to a file. Maybe worth renaming when you do the refactor work later.
| params: PullQueryParams, | ||
| meta: CommandMetaFlags | ||
| ) { | ||
| function fetchTextWrapper<TResponse>(cb: () => Promise<TResponse>) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What was the purpose of the wrapper function here instead of just putting the switch statement directly in the try block here?
joustrich
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couple minor comments, but otherwise looks good!
* [DIT-11970] iOS Strings Format Support (#129) * Add scaffolding for ios-strings support, notably IOSStringsFormatter class, and IOSStringsOutput file * Add /v2/variants endpoint. Update IOSStringsFormatter to pull down variants and projects as expected. Moved shared BaseFormatter class methods out of JSON and IOSStringsFormatters * Minor inline doc updates * Add pull command E2E tests for outputted ios-strings files. Added component mapping to iosStringsFormatter * Add unit tests to IOSSTringsFormatter class * Update variant fetching to be shared across textItems and components. Unit tests additions to IOSStringsFormatter class * Update http request tests to handle default error * Minor: test fix * Minor: cleanup and .gitignore of local items * [DIT-11792][DIT-11791][DIT-11960] IOS Strings Dict, Android, ICU format additions (#130) * Add ios-stringsdict support to BaseFormatter * Refactor IOSStringsFileFormatter into BaseExportFormatter to be shared amongst all export formats. Updated IOSStringsDict to use that class * Add android export format * Add BaseExportFormatter class tests. Updated IOSStringsFormatter tests to no longer include baseExport method tests. Updated all formats to test for correct output file creation * Update base generateQueryParams to take in filters as sole param * Add i18n test cases * Add ios-stringsdict and Android XML formatting tests to pull * Add ICU format. Update HTTP Response types to allow for JSON. Added generics to BaseFormatter to allow for parameter-ized response types * Updated ExportComponentsResponse and TextItemsResponse Zod schema * Made BaseExportFormatter abstract class * Minor: clean * Test fix and HTTP wrapper cleanup * Minor: clean * Add promise.all to fetchTextItemsMap and fetchComponentsMap for performance * [DIT-12000] Add iosLocales Configuration Support (#132) * Add iosLocale to config and file generation * Add new fetch request for swift file from API * Add Swift file generation logic to baseexport class * clean for PR * Add test cases to ios methods on baseExport class * Minor: clean * minor: remove unused type * minor: remove test script * update pull params for export endpoints * Update all instances of 'icu' to be 'json_icu' * Address initial PR comments * Add swift file generation to root of pull command. Address some cleanup review comments * Fix pull command tests for iosLocales * Move generateSwiftFile tests to util file * Minor clean * Remove console log and fix test data * Add test case for empty iosLocalese array * Minor name clarification * Fix format default case, missing promise.all, and typing issue * Added ios-specific getLocalesPath method to those classes, along with tests * Fix issue where ___<variant_id> suffixed files were getting written to iosLocale directories * Split up textItems and components HTTP calls for export vs default * Replaced all instances of 'base' with BASE_VARIANT_ID const in lib/src directory. Removed now-unnecessary type params from Formatter classes * Fix text item text status duplicates from merge. Bump version minor * Fix status filter merge issue * Fix to base variant not getting included in variants (id: all). minor cleanup of statuses qp * Add fetchVariants tests
Overview
IOSStringsFormatterto handleoutputswhereformat: ios-stringsBaseFormatterclass with shared format functionalityBaseFormatterclassGET /v2/textItems/exportandGET /v2/components/exportendpoint supportGET /v2/variantshttpGET /v2/projectshttppullcommand tests forios-stringsformat configContext
DIT-11970: [CLI] IOS Strings Format
Test Plan
Setup
.envlooks like the followingconfig.ymlin the./clirepository to organize formats intooutDirs. This is what mine looks likeAssertions
format: jsonwith noframeworkvariables.jsonfile at the root of the configuredoutDirwith your WS's variablesformat: jsonwith frameworki18nextindex.jsfile at the root of the configuredoutDirwith files exported as expectedios-stringsFormat works as expectedformat: ios-stringsoutDir(either at the project root config or in the output config)components___{variant}.stringsfile for each configured variant{project}___{variant}.stringsfile for each configured project/variant, e.g.variables.jsonfile. This is for typescript typing and not iOS stuff**im like 95% sure on this