[home] Fix tsc for expo-constants changes (#24312)# Why Types for classic manifests were removed in 50. This puts home in a weird state where it could still get classic updates but not have the
[home] Fix tsc for expo-constants changes (#24312)# Why Types for classic manifests were removed in 50. This puts home in a weird state where it could still get classic updates but not have the types for them. # How The fix that I applied here was just to design for EAS Update. In places that used to have special UI for classic updates, we now just show a generic UI. This is the lowest attention cost and is the fastest way forward (rather than reverting all the type changes and supporting classic manifest types for longer in the home app). # Test Plan `yarn tsc` # Checklist <!-- Please check the appropriate items below if they apply to your diff. This is required for changes to Expo modules. --> - [ ] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md). - [ ] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) - [ ] This diff will work correctly for `npx expo prebuild` & EAS Build (eg: updated a module plugin).
show more ...
[home] remove InfiniteScrollView and use FlatList-native infinite scroll props (#20914)# Why `InfiniteScrollView` is a legacy module from when Expo Go used `ListView`, which didn't have props f
[home] remove InfiniteScrollView and use FlatList-native infinite scroll props (#20914)# Why `InfiniteScrollView` is a legacy module from when Expo Go used `ListView`, which didn't have props for detecting end-of-list position for infinite scrolling purposes. We want to remove that module in this SDK release. # How Since we were already using `FlatList`, it was easy to simply remove `InfiniteScrollView` and use the `FlatList` props that serve our purposes. On top of replacing `InfiniteScrollView` prop usage, I followed the warnings in Apollo Client telling me that `updateQuery` is deprecated in favor of `typePolicies`, so I used their pagination helpers to achieve the same effect cache updating effect we had before. # Test Plan I opened the projects and snacks lists in Expo Go with this code running locally to make sure lists updated correctly and there were no more Apollo client warnings: https://user-images.githubusercontent.com/12488826/213896603-09b11640-c417-4f3b-9078-1af50da54979.mov I don't have any projects with enough branches to paginate, but it should behave the same as the other two lists.
update / fix usage of react-native-fade-in-image (#13148)Why Update version of react-native-fade-in-image to use provided type declarations. Also, fix misuse of props in two files. How Remove
update / fix usage of react-native-fade-in-image (#13148)Why Update version of react-native-fade-in-image to use provided type declarations. Also, fix misuse of props in two files. How Remove declare module react-native-fade-in-image type declaration and bump minor version in package.json. Removed use of nonexistent prop placeholderColor in two places. Test Plan Compile Expo Go locally to ensure no bugs or errors are caused by minor types update.
[home][2/2] Enforce noImplicitAny typescript setting (#12976)
[home] More typescript cleanup and types (#12975)
[home][chore] Convert redux to TypeScript (#9465)* Convert redux to TypeScript * Update Hooks.ts * Update Hooks.ts * fix IRecord * Updated types * Migrate App root component to TypeS
[home][chore] Convert redux to TypeScript (#9465)* Convert redux to TypeScript * Update Hooks.ts * Update Hooks.ts * fix IRecord * Updated types * Migrate App root component to TypeScript + hooks * Improve typing * Fix test mocking * default to no-preference theme
[home] Add typings & update Project-screen to TypeScript (#7954)* [home] Add typings * [home] Update ProjectScreen to TS and add typings * [home] Cleanup extractReleaseChannel