Rename unimodules imports to expo-modules-core
[localization] Add currency, separators, isMetric and update region (#11663)Adds the region property for Android and 4 new properties: currency, decimalSeparator, groupingSeparator and isMetric.
[localization] Added SSR support (#8824)* Added node support * fix iso code bug on web * Update CHANGELOG.md * Update packages/expo-localization/src/Localization.ts Co-authored-by: Mich
[localization] Added SSR support (#8824)* Added node support * fix iso code bug on web * Update CHANGELOG.md * Update packages/expo-localization/src/Localization.ts Co-authored-by: Michał Czernek <[email protected]> * updated build files Co-authored-by: Michał Czernek <[email protected]>
show more ...
[lint] Add "prefer-const" setting (#7389)* [lint] Add "prefer-const" setting See https://github.com/expo/expo/blob/master/guides/Expo%20JavaScript%20Style%20Guide.md#let-and-const which explains
[lint] Add "prefer-const" setting (#7389)* [lint] Add "prefer-const" setting See https://github.com/expo/expo/blob/master/guides/Expo%20JavaScript%20Style%20Guide.md#let-and-const which explains the overall rationale for using `const` (mainly to pick a lintable option and to reduce attention cost talking about it). Tested by adding a test case to the linter and running tests and looking at the snapshot to see that the linter autofixed let to const. * [lint] Apply let/const autofixes * Add build files
[lint] Upgrade Prettier to 1.19 and other ESLint dependenciesPrettier 1.19 has support for null coalescing, which we need for TypeScript 3.7.
[lint] Add a "lint" script to all packages and fix lint warnings & errorsThis turns on linting for all of the packages, enforced by `expotools check-packages`. I added a "lint" script to each packa
[lint] Add a "lint" script to all packages and fix lint warnings & errorsThis turns on linting for all of the packages, enforced by `expotools check-packages`. I added a "lint" script to each package and an `.eslintrc.js` file created by expo-module-scripts. For some packages like jest-expo that are intended to run on Node, I used a small handwritten ESLint config that uses the universe/node config.Tested with `expotools check-packages` after fixing all the lint warnings and errors.
[Localization] Introduce `Localization.region` (#4921)# Why Resolve #4540. # How Country variable on Android came from currently selected language, however on devices with iOS country was
[Localization] Introduce `Localization.region` (#4921)# Why Resolve #4540. # How Country variable on Android came from currently selected language, however on devices with iOS country was got from `Region` in `Language & Region`. Not all android phone provide `Region` setting, so I suggest renaming Localization.country to Localization.region and make it available only on iOS. # Test Plan You can check it on https://snack.expo.io/@lukaszkosmaty/9e807b. I also updated test-suits.
Migrate expo-localization to TypeScript (#3398)* Migrated to TypeScript * Added tests * Update config.yml * Update LocalizationScreen.js * Update Expo.ts * Update packages/expo-local
Migrate expo-localization to TypeScript (#3398)* Migrated to TypeScript * Added tests * Update config.yml * Update LocalizationScreen.js * Update Expo.ts * Update packages/expo-localization/README.md Co-Authored-By: EvanBacon <[email protected]> * Fixed API * Update Localization-test.ts * Remoevd type export