[blur] Support more blur effects (#24392)
[expo-blur] Fix reanimated support for BlurView (#22783)# Why Our demo screen for `BlurView` has stopped working. # How > NOTE: `getAnimatableRef` relies on this reanimated PR: https://gi
[expo-blur] Fix reanimated support for BlurView (#22783)# Why Our demo screen for `BlurView` has stopped working. # How > NOTE: `getAnimatableRef` relies on this reanimated PR: https://github.com/software-mansion/react-native-reanimated/pull/4533. Don't merge this PR until the Reanimated feature gets approved by the Reanimated team. On iOS and Android added the `getAnimatableRef` function, which passes the `NativeBlurView` to `reanimated` as the animatable component when user calls the `Animated.createAnimatedComponent`. On web used `setNativeProps` to add reanimated support (it wasn't working correctly before). It would be too complicated to support both `Animated API` and `react-native-reanimated`, so support for animating intensity with `Animated API` has been dropped. # Test Plan Tested on Android, iOS and web > Demo video might not work on Safari due to my recording settings, it works ok on Google Chrome https://github.com/expo/expo/assets/31368152/a5095c99-12a4-4be2-9e04-0e6b80e7ecb3 --------- Co-authored-by: Expo Bot <[email protected]>
show more ...
feat(blur): enable blurring by default when static rendering. (#23000)# Why This is technically not correct but does provide a better default for SSG with Expo Router. Ultimately we should incl
feat(blur): enable blurring by default when static rendering. (#23000)# Why This is technically not correct but does provide a better default for SSG with Expo Router. Ultimately we should include CSS or some sort of static extraction that uses media queries instead of JS. Perhaps in SDK 50 when/if we enable CSS by default in Metro, then we can change this again. <!-- Please describe the motivation for this PR, and link to relevant GitHub issues, forums posts, or feature requests. --> # How Default to blurring being supported when static rendering. <!-- How did you build this feature or fix this bug and why? --> # Test Plan Run in an Expo Router v2 project with JS disabled. <!-- Please describe how you tested this change and how a reviewer could reproduce your test, especially if this PR does not include automated tests! If possible, please also provide terminal output and/or screenshots demonstrating your test/reproduction. --> # 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). --------- Co-authored-by: Expo Bot <[email protected]>
Fix all failing SDK checks
[expo-blur][Android] Add support for BlurView on Android (#21744)# Why There was no support for `BlurView` on android. Instead of blurring the view would just set the background color to semitr
[expo-blur][Android] Add support for BlurView on Android (#21744)# Why There was no support for `BlurView` on android. Instead of blurring the view would just set the background color to semitransparent. # How Using [BlurView](https://github.com/Dimezis/BlurView) library and Modules API added blur support for Android. Default prop settings match it quite closely with the iOS version. # Test Plan Tested on Android emulators (API 33 and 28), and a physical device (API 31). Also compared the look of the blur on android emulator to the iOS simulator. --------- Co-authored-by: Expo Bot <[email protected]>
Add `WebkitBackdropFilter` to support `react-native-web` styling. (#21146)# Why RNW is asserting that the style name needs to be pascal case --------- Co-authored-by: Expo Bot <34669131+ex
Add `WebkitBackdropFilter` to support `react-native-web` styling. (#21146)# Why RNW is asserting that the style name needs to be pascal case --------- Co-authored-by: Expo Bot <[email protected]>
fix(expo-blur): add `-webkit-backdrop-filter` to support blurring on Safari. (#21003)# Why Seems like react-native-web no longer auto prefixes styles, this PR adds the prefixed styles back for
fix(expo-blur): add `-webkit-backdrop-filter` to support blurring on Safari. (#21003)# Why Seems like react-native-web no longer auto prefixes styles, this PR adds the prefixed styles back for blurring on Safari. --------- Co-authored-by: Expo Bot <[email protected]>
[2/3] upgrade react native 0.71 (#20832)# Why follow up #20799 for react-native 0.71 upgrade. this pr aims for jest upgrade and fix all broken tests. close ENG-7192 # How - upgrade packag
[2/3] upgrade react native 0.71 (#20832)# Why follow up #20799 for react-native 0.71 upgrade. this pr aims for jest upgrade and fix all broken tests. close ENG-7192 # How - upgrade packages - `jest: ^26.0.24 -> ^29.2.1` - `jest-watch-typeahead: 0.6.4 -> 2.2.1` - `@types/jest: ^26.0.24 -> ^29.2.1` - `babel-jest: ^26.6.3 -> ^29.2.1` - `@jest/create-cache-key-function: ^27.0.1 -> ^29.2.1` - `@babel/preset-env: ^7.12.9 -> ^7.14.0` - `eslint: ^8.20.0 -> ^8.29.0` - add `jest-environment-jsdom` because new jest does not include it by default - [core] fix `SyntheticPlatformEmitter` type error. originally it refers to `react-native/Libraries/EventEmitter/RCTDeviceEventEmitter` internal file which has incorrect type setup in 0.71. we could use the `react-native.DeviceEventEmitter` instead. - [expo-linking]: remove the deprecated `Linking.removeEventListener` (which is also removed from upstream) - [firebase-recaptcha] remove broken web test because firebase ESM which is not supported by jest. this pr simply remove the test case because the package is deprecated. - [jest-expo-enzyme] remove this package and move to [the archived repo](https://github.com/expo/jest-expo-enzyme). enzyme cannot upgrade to jest 29. - remove `@types/react-native` and the versioned cli package check. because 0.71 ships the types directly. - [ncl] workaround `@react-native-community/slider`, `@react-native-segmented-control/segmented-control`, and `@react-native-masked-view/masked-view` type errors in the `react-native-71-fix.d.ts`. - for other details, please check the commit histories one by one. # Test Plan - ci passed - for test-suite ios ci error, i've mentioned in #20799
[blur] add basic JSDoc comment to the exported component (#20698)
[ios] Migrate expo-blur to the new native modules API (#19786)
Fix check-packages on CI broken due to enzyme removal (#19791)
[packages] fix ci errors (#18028)
[lur] tweak types for docs extraction (#15654)
[blur][iOS] Rewritten module to blur text content properly on iOS (#14946)
[eslint-config] remove `arrowParens` overwrite, reformat files (#14232)
[eslint-config] bump dependencies and minimum required lint tools versions (#13858)Co-authored-by: James Ide <[email protected]>
[blur] web: fix bug with too high `intensity`, update tint colors (#14112)* [blur] web: fix bug with too high `intensity`, update tint colors * add web test which checks max blur and color opaci
[blur] web: fix bug with too high `intensity`, update tint colors (#14112)* [blur] web: fix bug with too high `intensity`, update tint colors * add web test which checks max blur and color opacity values * Update packages/expo-blur/CHANGELOG.md Co-authored-by: Expo CI <[email protected]> Co-authored-by: Expo CI <[email protected]>
Rename unimodules imports to expo-modules-core
[blur] add doc comments in source (#12277)
[blur] Fix types - tint now a string union `'dark' | 'light' | 'default'` rather than any string (#12264)
[blur] explicitly pass down props on iOS (#10648)
[blur] Convert Android and web to class components (#8856)* Convert Android and web to class components * Update BlurView-test.web.tsx * Update CHANGELOG.md
[blur] Delete prop-types (#8676)* Delete prop-types - convert to functional components * change export * Update CHANGELOG.md * Updated blur view types * Update packages/expo-blur/CHA
[blur] Delete prop-types (#8676)* Delete prop-types - convert to functional components * change export * Update CHANGELOG.md * Updated blur view types * Update packages/expo-blur/CHANGELOG.md * Forward setNativeProps * Fixed useNativeDriver warning in NCL * Revert BlurView.ios to a class component
Use saturation filter and new colors (#7567)
[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
12