-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
appx manifest - supported languages #1684
Comments
I have assigned you to fix it ;) |
Our test suite currently doesn't unpack appx and doesn't verify manifest — test will be not easy to write. |
Aight.
|
@black-snow In case of Info.plist we remove some always changed fields and then toMatchSnapshot(). Will be cool if you will add such functionality to test appx. |
Thanks for the hint. |
BTW, so disappointing that we cannot run makeappx on mac/linux :( |
This is the first time I'm actually doing something in typescript. Implementation should be done. After a quick glimpse at jest snapshot testing I'm really confused. Where are those snapshots? How would I add one? How would that snapshot look like? * Serialized* manifest? appx?
|
Jest automatically creates snapshot file on first run. Appx test check that appx produces some files, but appx works only on Windows. I will grab your changes and will commit :) |
@black-snow Thanks! |
@develar You're welcome. |
It's great to have some improved appx support for I can drop a lot of custom scripts. Now there's one thing I'm still missing and that's support for listing supported languages in the appx manifest. Currently
en-US
is the default one and that can't be changed easily. (I'm unpacking the appx, changing the manifest, packing, signing.)See: https://docs.microsoft.com/en-us/windows/uwp/globalizing/manage-language-and-region#specify-the-supported-languages-in-the-apps-manifest
I'd like to state the supported languages in my build config like:
Where the first one's the default language. It should default to
en-US
.I'll try to file a PR if you aren't faster ;)
The text was updated successfully, but these errors were encountered: