-
-
Notifications
You must be signed in to change notification settings - Fork 218
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
feat: Compose multiplatform strings import & export #2649
base: main
Are you sure you want to change the base?
Conversation
6aa07de
to
8812d76
Compare
abe6d79
to
b149de6
Compare
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.
Looks good!
@@ -59,8 +59,8 @@ class AndroidXmlFileExporterTest { | |||
|<resources xmlns:xliff="urn:oasis:names:tc:xliff:document:1.2"> | |||
| <string name="i_am_array_english">This is english!</string> | |||
| <plurals name="plural_with_placeholders"> | |||
| <item quantity="one">%s dog</item> | |||
| <item quantity="other">%s dogs</item> | |||
| <item quantity="one">%1${'$'}s dog</item> |
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.
Is this correct?
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.
I believe it is. One of the changes this PR makes is that both Android and Compose Multiplatform will always use numbered placeholders from now on (also mentioned in the original issue: #2397 (comment)). Tests were adjusted to accompany this change. Is this okay, or did I miss something?
de2f716
to
487f8bd
Compare
Fixes #2397