satya164

satya164

JavaScript is life's love!

Member Since 10 years ago

@callstack , Wrocław, Poland

Experience Points
2k
follower
Lessons Completed
0
follow
Lessons Completed
172
stars
Best Reply Awards
89
repos

1735 contributions in the last year

Pinned
⚡ Simple no-frills code editor with syntax highlighting
⚡ A better way of working with web workers
⚡ Jest matcher to write snapshots to a separate file instead of the default snapshot file used by Jest
⚡ An opinionated library to make testing babel plugins easier.
⚡ Babel plugin to optionaly require modules
⚡ A cross-platform Tab View component for React Native
Activity
Jan
18
22 hours ago
push

satya164 push callstack/react-native-paper

satya164
satya164

Deploy to GitHub Pages: e049a467800ea8a6b4f922e5122db77a5fb41e3f

commit sha: 2af099e5df5cfd89966502cbb52fae5e2983715a

push time in 12 hours ago
Jan
17
1 day ago
Activity icon
issue

satya164 issue comment react-navigation/react-navigation

satya164
satya164

undefined is not an object(evaluating '_$$_REQUIRE(_dependencyMap[0], "@react-navigation/core").NavigationActions.init')

Current behavior

I want to mix up redux and react-navigation, but a bug presents after I followed the steps in the internet.

Anyway, I find that maybe the problem is in "getStateForAction" of "@react-navigation/core" by steps debug.

the details can be found in my repository "bugDemo" [readme.md]

the redux config is at "/src/store/index.js"

Expected behavior

it should be normal, or return null even if "getStateforAction()" can't handle as official docs said.

"https://reactnavigation.org/docs/2.x/custom-routers/#getstateforactionaction-state"

Reproduction

https://github.com/qgao233/bugDemo/tree/master

Platform

  • Android
  • iOS
  • Web
  • Windows
  • MacOS

Packages

Environment

package version
@react-navigation/native "^6.0.6"
@react-navigation/bottom-tabs
@react-navigation/drawer
@react-navigation/material-bottom-tabs
@react-navigation/material-top-tabs
@react-navigation/stack
@react-navigation/native-stack "^6.2.5"
react-native-safe-area-context "^3.3.2"
react-native-screens "^3.10.1"
react-native-gesture-handler
react-native-reanimated
react-native-tab-view
react-native-pager-view
react-native "0.64.0"
expo
node "12.22.5"
npm or yarn
"react-navigation-redux-helpers" "^4.0.1",
"react-redux" "^7.2.6",
"redux" "^4.1.2"
satya164
satya164

react-navigation-redux-helpers is deprecated and only works with very old versions as indicated in the README https://github.com/react-navigation/redux-helpers

Activity icon
issue

satya164 issue react-navigation/react-navigation

satya164
satya164

undefined is not an object(evaluating '_$$_REQUIRE(_dependencyMap[0], "@react-navigation/core").NavigationActions.init')

Current behavior

I want to mix up redux and react-navigation, but a bug presents after I followed the steps in the internet.

Anyway, I find that maybe the problem is in "getStateForAction" of "@react-navigation/core" by steps debug.

the details can be found in my repository "bugDemo" [readme.md]

the redux config is at "/src/store/index.js"

Expected behavior

it should be normal, or return null even if "getStateforAction()" can't handle as official docs said.

"https://reactnavigation.org/docs/2.x/custom-routers/#getstateforactionaction-state"

Reproduction

https://github.com/qgao233/bugDemo/tree/master

Platform

  • Android
  • iOS
  • Web
  • Windows
  • MacOS

Packages

Environment

package version
@react-navigation/native "^6.0.6"
@react-navigation/bottom-tabs
@react-navigation/drawer
@react-navigation/material-bottom-tabs
@react-navigation/material-top-tabs
@react-navigation/stack
@react-navigation/native-stack "^6.2.5"
react-native-safe-area-context "^3.3.2"
react-native-screens "^3.10.1"
react-native-gesture-handler
react-native-reanimated
react-native-tab-view
react-native-pager-view
react-native "0.64.0"
expo
node "12.22.5"
npm or yarn
"react-navigation-redux-helpers" "^4.0.1",
"react-redux" "^7.2.6",
"redux" "^4.1.2"
Jan
16
2 days ago
Activity icon
issue

satya164 issue satya164/react-native-tab-view

satya164
satya164

Jcenter needs to be removed

Current behavior

Jcenter is not stable at the moment and its support will be discontinued. I am trying to compile my app locally and I getting this issue due to jcenter

Could not download kotlin-build-common-1.5.30.jar (org.jetbrains.kotlin:kotlin-build-common:1.5.30)

Could not get resource 'https://jcenter.bintray.com/org/jetbrains/kotlin/kotlin-build-common/1.5.30/kotlin-build-common-1.5.30.jar'. > Could not GET 'https://jcenter.bintray.com/org/jetbrains/kotlin/kotlin-build-common/1.5.30/kotlin-build-common-1.5.30.jar'. Received status code 502 from server: Bad Gateway

Expected behavior

app builds successfully

Reproduction

https://jcenter.bintray.com/org/jetbrains/kotlin/kotlin-build-common/1.5.30/kotlin-build-common-1.5.30.ved

Platform

  • Android
  • iOS
  • Web
  • Windows
  • MacOS

Environment

package version
react-native-tab-view
react-native-pager-view
react-native
expo
node
npm or yarn
Activity icon
issue

satya164 issue comment satya164/react-native-tab-view

satya164
satya164

Jcenter needs to be removed

Current behavior

Jcenter is not stable at the moment and its support will be discontinued. I am trying to compile my app locally and I getting this issue due to jcenter

Could not download kotlin-build-common-1.5.30.jar (org.jetbrains.kotlin:kotlin-build-common:1.5.30)

Could not get resource 'https://jcenter.bintray.com/org/jetbrains/kotlin/kotlin-build-common/1.5.30/kotlin-build-common-1.5.30.jar'. > Could not GET 'https://jcenter.bintray.com/org/jetbrains/kotlin/kotlin-build-common/1.5.30/kotlin-build-common-1.5.30.jar'. Received status code 502 from server: Bad Gateway

Expected behavior

app builds successfully

Reproduction

https://jcenter.bintray.com/org/jetbrains/kotlin/kotlin-build-common/1.5.30/kotlin-build-common-1.5.30.ved

Platform

  • Android
  • iOS
  • Web
  • Windows
  • MacOS

Environment

package version
react-native-tab-view
react-native-pager-view
react-native
expo
node
npm or yarn
satya164
satya164

This library doesn't include any native code. Please open the issue in the relevant library's repo.

Jan
15
3 days ago
push

satya164 push satya164/dotfiles

satya164
satya164

use the forked syntax highlight plugin

satya164
satya164

commit sha: 9d1fe37cdc48a192c08efd1cf4701a8130e77bd5

push time in 3 days ago
Jan
13
5 days ago
push

satya164 push react-navigation/react-navigation

satya164
satya164

chore: add a checkbox to confirm that people remove the packagesthat they don't use

commit sha: e9c690450068d29a2ce62004992ad75d626ca0c2

push time in 5 days ago
Jan
12
6 days ago
pull request

satya164 merge to react-navigation/react-navigation.github.io

satya164
satya164

docs: mention index is always last route in a stack

READ ME PLEASE!

TL;DR: Make sure to add your changes to versioned docs

Thanks for opening a PR!

The docs cover several versions of react-navigation, and in some cases there are several files (for version 1, version 2 and etc.) that all describe a single page of the docs (eg. "Getting Started").

Please make sure that the edit you're making in docs/file-you-edited.md is also included in the file for the correct version, eg. /versioned_docs/version-3.x/file-you-edited.md for version 3. If such file doesn't exist, please create it. :+1:


Hi there, this change make the docs mention this, in case a developer tries to specify a value for index apart that is not equal to the last route in a stack and sees that it has no effect, eg. issue #10056.

satya164
satya164

Thanks for the PR. I think adding "For example..." to the existing paragraph feels a bit out of place. I'd create a new paragraph for this.

However, the exact structure of navigation state is described in a separate document and it also talks about invalid states & corrections (under "Partial state objects"), so I feel like it'd be better to link there directly instead of adding this here. People need to be familiar with state object to use reset anyway, so that page is a pre-requisite.

https://reactnavigation.org/docs/navigation-state/

Jan
11
1 week ago
push

satya164 push react-navigation/react-navigation.github.io

satya164
satya164

Deploy website - based on 514e3cf4d40268fff979f66f16f3ea942ddf19c2

commit sha: 7ba2877fdd5e148ef7891083abb968eaf489abea

push time in 1 week ago
push

satya164 push react-navigation/react-navigation.github.io

satya164
satya164

Deploy website - based on 2f4be5aad55474bbe50b0774969f03c6007edf2d

commit sha: 61deb0881a9a2299f3bbf5712a1e1ea302d8a233

push time in 1 week ago
Jan
3
2 weeks ago
Activity icon
issue

satya164 issue comment callstack/react-native-builder-bob

satya164
satya164

Watch command is not rebuilding

Maybe I'm using "watch" incorrectly.

I want to watch for changes under the './src/' directory.

When I make a change all I see is message stating it's a directory, the rebuild is not triggered...

➜ yyy-ui-components git:(master) ✗ yarn watch ./src/ yarn run v1.22.10 $ /Users/xxx/workspace/nextga/yyy-ui-components/node_modules/.bin/watch ./src/

Watching /Users/xxx/workspace/yyy/yyy-ui-components sh: ./src/: is a directory sh: ./src/: is a directory sh: ./src/: is a directory

satya164
satya164

it's not working like you described, building is required on every change.

If it's not working then please open an issue with a repro. Though I have been using this in several libraries and never had an issue. Unless you changed something in the way the example app is configured (babel alias, package.json keys, metro config), then there's no reason it wouldn't work.

Dec
31
2 weeks ago
Activity icon
issue

satya164 issue comment react-navigation/react-navigation

satya164
satya164

feat(material top tab): add callback for tab index change

I would like to know the new tab index when tab is changed so I created this PR

satya164
satya164

Hey, thanks a lot for the PR. But you can already check when the index changes using the state listener on the screenListeners prop https://reactnavigation.org/docs/navigation-events/#screenlisteners-prop-on-the-navigator

Dec
29
2 weeks ago
Activity icon
issue

satya164 issue comment react-navigation/react-navigation

satya164
satya164

Header-Height changes when card-modal is being dragged on iOS

Current behavior

The height of the header inside of a card-style modal on iOS changes as the user drags the modal to the top (rubber-band-effect). (See Video)

https://user-images.githubusercontent.com/36629890/147644036-27c83f8d-4f18-460e-bd88-451dad9c9474.MP4

Expected behavior

The height of the header should be consistent.

Reproduction

https://snack.expo.dev/Kf-5XUujGQ

Platform

  • Android
  • iOS
  • Web
  • Windows
  • MacOS

Packages

Environment

package version
@react-navigation/native 6.0.6
@react-navigation/bottom-tabs 6.0.9
@react-navigation/stack 6.0.11
@react-navigation/native-stack 6.2.5
react-native-safe-area-context 3.3.2
react-native-screens 3.10.1
react-native-gesture-handler 2.1.0
react-native-reanimated 2.3.1
react-native 0.64.3
expo 44.0.0
node 14.17.0
npm or yarn yarn 1.22.10
Dec
27
3 weeks ago
Activity icon
issue

satya164 issue comment react-navigation/react-navigation

satya164
satya164

Padding not applied in Screens with header

Current behavior

After upgrading to Expo SDK 44, Screens with the default header don't add a top margin to the content. As a result, the content is hidden behind the header.

The navigation stack:

    <NavigationContainer>
      <Stack.Navigator initialRouteName="Home">
        <Stack.Screen
          name="Home"
          component={HomeScreen}
          options={{ headerStyle: { backgroundColor: "#a005" } }}
        />
        <Stack.Screen name="Details" component={DetailsScreen} />
      </Stack.Navigator>
    </NavigationContainer>

The HomeScreen:

function HomeScreen({ navigation }) {
  return (
    <View
      style={{ flex: 1 }}
    >
      <Text>This is top text.</Text>
    </View>
  );
}

Result: image

Expected behavior

Before upgrading to Expo SDK 44, Screens with header visible would add their content right below the header.

In fact, the React Navigation docs (handling safe area) give a clear example about this expected behaviour: "React Navigation handles safe area in the default header."

The following picture shows the expected behaviour: image

The Reproduction code is that of the expected behaviour because Snack doesn't allow me to use Expo 44.

Reproduction

https://snack.expo.dev/CW-D_Jbre

Platform

  • Android
  • iOS
  • Web
  • Windows
  • MacOS

Packages

Environment

package version
@react-navigation/native 6.0.6
@react-navigation/native-stack 6.2.5
react-native-safe-area-context 3.3.2
react-native-screens 3.10.1
react-native 0.64.3
expo 44.0.0
node 16.13.1
npm or yarn yarn 1.22.17
Dec
22
3 weeks ago
Activity icon
issue

satya164 issue react-navigation/react-navigation

satya164
satya164

Navigating into a screen deep in not mounted stack

Current Behavior

I have a stack inside a drawer item. I'm navigating to a screen that is not the initial screen of the stack after opening a notification (either in background or foreground). This works but how to build the navigation actions so I can go back from the screen that's deep? Even if I change the item in the drawer the next time I come back the "deep" screen is mounted.

Expected Behavior

I can navigate to a route deep in a stack and set up a hierarchy so it's possible to come back the usual way. Or be able to leave the stack (switch to another one in the drawer) and next time open stack with initial screen open.

How to reproduce I'm trying something like this

containerRef.current.dispatch(
            CommonActions.navigate({
              name: "Root", // Drawer navigator name
              params: {
                screen: "First", // Name of the first item in drawer navigator
                params: {
                  screen: "screen2" // screen deep in the stack
                }
              },
              source: 'screen1'
            })
          )

Expo app: https://expo.io/@radko93/nav-repro Repro code: https://github.com/radko93/nav-repro/blob/master/App.js

Your Environment

software version
iOS or Android both
@react-navigation/native latest
@react-navigation/stack latest
react-native-gesture-handler
react-native-safe-area-context
react-native-screens 2.2.0
react-native
expo 37
node 13
npm or yarn yarn
Activity icon
issue

satya164 issue comment react-navigation/react-navigation

satya164
satya164

Navigating into a screen deep in not mounted stack

Current Behavior

I have a stack inside a drawer item. I'm navigating to a screen that is not the initial screen of the stack after opening a notification (either in background or foreground). This works but how to build the navigation actions so I can go back from the screen that's deep? Even if I change the item in the drawer the next time I come back the "deep" screen is mounted.

Expected Behavior

I can navigate to a route deep in a stack and set up a hierarchy so it's possible to come back the usual way. Or be able to leave the stack (switch to another one in the drawer) and next time open stack with initial screen open.

How to reproduce I'm trying something like this

containerRef.current.dispatch(
            CommonActions.navigate({
              name: "Root", // Drawer navigator name
              params: {
                screen: "First", // Name of the first item in drawer navigator
                params: {
                  screen: "screen2" // screen deep in the stack
                }
              },
              source: 'screen1'
            })
          )

Expo app: https://expo.io/@radko93/nav-repro Repro code: https://github.com/radko93/nav-repro/blob/master/App.js

Your Environment

software version
iOS or Android both
@react-navigation/native latest
@react-navigation/stack latest
react-native-gesture-handler
react-native-safe-area-context
react-native-screens 2.2.0
react-native
expo 37
node 13
npm or yarn yarn
satya164
satya164

Please open a new issue with repro

Activity icon
issue

satya164 issue comment react-navigation/react-navigation

satya164
satya164

Theme change not being applied to header of NativeStack for `presentation: "modal"`

Current behavior

When changing themes on iOS, the theme is not applied to the header of a NativeStack Screen which is behind a presentation: "modal" screen. This only applies to the screen directly behind the modal screen -- e.g. If a modal is in front of two tabs, only the in-focus tab has this issue. Additionally, the issue goes away after swapping to a different screen and back again.

It works correctly on other presentations.

I've attempted to hack around this by directly setting the options: { headerStyle }, however this doesn't fix it -- it seems like the header just isn't getting triggered to rerender at all when under the modal screen.

I've included a Snack of this behavoir, here's the code:

Code Reproduction
import * as React from 'react';
import { Text, View, Switch, TouchableOpacity, StyleSheet } from 'react-native';

import { NavigationContainer } from '@react-navigation/native';
import { createNativeStackNavigator } from '@react-navigation/native-stack';
import { DefaultTheme, DarkTheme } from '@react-navigation/native';

const Stack = createNativeStackNavigator();

export default function App() {
  const [theme, setTheme] = React.useState('light');
  return (
    <NavigationContainer theme={theme === 'dark' ? DarkTheme : DefaultTheme}>
      <Stack.Navigator>
        <Stack.Screen
          name="Home"
          component={({ navigation }) => (
            <View style={styles.Container}>
              <TouchableOpacity
                style={styles.Button}
                onPress={() => {
                  navigation.navigate('Settings');
                }}>
                <Text> Open Settings </Text>
              </TouchableOpacity>
            </View>
          )}
        />
        <Stack.Screen
          options={{
            presentation: 'modal',
          }}
          name="Settings"
          component={() => (
            <View style={styles.Container}>
              <Text> Dark Mode: </Text>
              <Switch
                value={theme === 'dark'}
                onValueChange={(isDark) =>
                  void setTheme(isDark ? 'dark' : 'light')
                }
              />
            </View>
          )}
        />
      </Stack.Navigator>
    </NavigationContainer>
  );
}

const styles = StyleSheet.create({
  Container: {
    flex: 1,
    justifyContent: 'center',
    alignItems: 'center',
  },
  Button: {
    padding: 12,
    backgroundColor: 'gray',
    borderWidth: 1,
    borderRadius: 12,
    width: 200,
    justifyContent: 'center',
    alignItems: 'center',
  },
});

Expected behavior

The theme provider should update the header component of the screen underlying the modal-presentation screen.

Reproduction

https://snack.expo.dev/@jacobjaffe/react-navigation---presentation-modal-theme-bug

Platform

  • Android
  • iOS
  • Web
  • Windows
  • MacOS

Packages

Environment

package version
@react-navigation/native "^6.0.6"
@react-navigation/native-stack "^6.2.5"
Dec
16
1 month ago
Activity icon
issue

satya164 issue react-navigation/react-navigation

satya164
satya164

goBack to previous screen with parameters

Current behavior

The user can goBack from screen B to screen A using the swipe back gesture or pressing the back button. When this happen I just want to pass from screen B to screen A some parameters like user selected option.

I use e.preventDefault(); and then dispatch an action like navigation.dispatch( CommonActions.navigate({ name: 'ReturningScreens', params: { option: 'A', }, }), ); but simply doesn't work this way, I receive an Error Simulator Screen Shot - iPhone 12 mini - 2021-11-15 at 12 57 04

Expected behavior

I would like to have a simple solution like either using navigation.goBack() with parameters or dispatching a POP action with parameters to automatically update the screen A params when coming from screen B

Reproduction

https://snack.expo.dev/

Platform

  • Android
  • iOS
  • Web
  • Windows
  • MacOS

Packages

Environment

package version
@react-navigation/stack 6.0.11
@react-navigation/native-stack 6.2.5
Activity icon
issue

satya164 issue comment react-navigation/react-navigation

satya164
satya164

goBack to previous screen with parameters

Current behavior

The user can goBack from screen B to screen A using the swipe back gesture or pressing the back button. When this happen I just want to pass from screen B to screen A some parameters like user selected option.

I use e.preventDefault(); and then dispatch an action like navigation.dispatch( CommonActions.navigate({ name: 'ReturningScreens', params: { option: 'A', }, }), ); but simply doesn't work this way, I receive an Error Simulator Screen Shot - iPhone 12 mini - 2021-11-15 at 12 57 04

Expected behavior

I would like to have a simple solution like either using navigation.goBack() with parameters or dispatching a POP action with parameters to automatically update the screen A params when coming from screen B

Reproduction

https://snack.expo.dev/

Platform

  • Android
  • iOS
  • Web
  • Windows
  • MacOS

Packages

Environment

package version
@react-navigation/stack 6.0.11
@react-navigation/native-stack 6.2.5
satya164
satya164

You're preventing the action to go back, the dispatching an action to go back, then preventing it, then dispatching it again, and so on...

You need to check which action you want to prevent and which you don't by checking e.data.action.

Dec
15
1 month ago
Activity icon
issue

satya164 issue comment facebook/react-native

satya164
satya164

Flex gap

Implements rowGap and columnGap. Creating a draft PR for testing. Will update this section soon! Feedbacks are welcome.

To test the example

  • Run rn-tester as per the instructions in readme.md. I've modified RNTesterAppShared.js with flex gap example.

Note: Only works on iOS. Android probably needs some small changes in yoga bindings. Will look into it

https://user-images.githubusercontent.com/23293248/146173072-bce93401-cd37-413a-bd3e-40efda38a59a.mov

satya164
satya164

Would also be cool to support gap property which is a shorthand for both row-gap and column-gap

Dec
12
1 month ago
push

satya164 push callstack/react-native-paper

satya164
satya164

Deploy to GitHub Pages: 3c916b731417cd0d5b21416a76aade35be0d7c88

commit sha: df6d6a5d9324e2b938d588a16734b7fc8244c950

push time in 1 month ago
Dec
10
1 month ago
push

satya164 push callstack/react-native-paper

satya164
satya164

Deploy to GitHub Pages: 6c2e53457c9f3818d11eb3e325e105e145c6fa55

commit sha: 233f612c4b026ece1363afeea495411dbb1c354a

push time in 1 month ago
push

satya164 push callstack/react-native-paper

satya164
satya164

Deploy to GitHub Pages: abf631a4d595831fcd12be03008be059bb5aeeec

commit sha: 55c30997d856a8a64f840dda4df4aa1fd610b77b

push time in 1 month ago
push

satya164 push callstack/react-native-paper

satya164
satya164

Deploy to GitHub Pages: 69d5ffedb71388350a95bf9e3425a32f845e1991

commit sha: 0a7bb56ab1c588e080256e688a53f2d0043fef3d

push time in 1 month ago
Dec
5
1 month ago
Activity icon
issue

satya164 issue comment torgeadelin/react-native-animated-nav-tab-bar

satya164
satya164

Error: Couldn't register the navigator.

Hello i ran into some issues, I'm building the app with expo and react-navigation v5 but i got this error when i tried to view the app on my device

Error: Couldn't register the navigator. Have you wrapped your app with 'NavigationContainer'?

This error is located at: in BottomTabNavigator (at AnimatedTab.js:30) in EnsureSingleNavigator (at BaseNavigationContainer.tsx:409) in ForwardRef(BaseNavigationContainer) (at NavigationContainer.tsx:91) in ThemeProvider (at NavigationContainer.tsx:90) in ForwardRef(NavigationContainer) (at AnimatedTab.js:27) in TabNav (at App.js:86) in ThemeProvider (at App.js:82) in App (created by ExpoRoot) in ExpoRoot (at renderApplication.js:45) in RCTView (at View.js:34) in View (at AppContainer.js:106) in RCTView (at View.js:34) in View (at AppContainer.js:132) in AppContainer (at renderApplication.js:39)

and yes i wrapped the app with NavigationContainer, please can u help me out? thank youi

satya164
satya164

@torgeadelin you have exact version in peer dependency which will still cause the issue with npm and print warning on yarn. You have to use a version range such as >= 5.0.0 || >= 6.0.0 or use * for any version.

Dec
1
1 month ago
push

satya164 push callstack/react-native-paper

satya164
satya164

Deploy to GitHub Pages: 85d679ea99df0a6090e4a0dce7a57fe4fa7536d6

commit sha: 6dee81aba2f443436058d0237c07637327d9ff2e

push time in 1 month ago
Nov
30
1 month ago
Activity icon
issue

satya164 issue react-navigation/react-navigation

satya164
satya164

useNavigation -> navigate causes typeScript error

Current behavior

If you use navigation.navigate("screenName") with useNavigation, you get the following typeScript error. Everything is working fine.

Bildschirmfoto 2021-11-29 um 22 20 44

Expected behavior

No Error

Reproduction

See Code in Screenshot

Platform

  • Android
  • iOS
  • Web
  • Windows
  • MacOS

Packages

Environment

"@react-navigation/bottom-tabs": "^6.0.9", "@react-navigation/native": "^6.0.6", "@react-navigation/native-stack": "^6.1.0",

Activity icon
issue

satya164 issue comment react-navigation/react-navigation

satya164
satya164

useNavigation -> navigate causes typeScript error

Current behavior

If you use navigation.navigate("screenName") with useNavigation, you get the following typeScript error. Everything is working fine.

Bildschirmfoto 2021-11-29 um 22 20 44

Expected behavior

No Error

Reproduction

See Code in Screenshot

Platform

  • Android
  • iOS
  • Web
  • Windows
  • MacOS

Packages

Environment

"@react-navigation/bottom-tabs": "^6.0.9", "@react-navigation/native": "^6.0.6", "@react-navigation/native-stack": "^6.1.0",

satya164
satya164

Closing since this is covered in docs and there are several issues you could find if you searched before opening an issue.

Nov
28
1 month ago
Activity icon
issue

satya164 issue comment callstack/react-native-pager-view

satya164
satya164

Update ReactNativePageView.m

resolve rtl support

Summary

Test Plan

What's required for testing (prerequisites)?

What are the steps to reproduce (after prerequisites)?

Compatibility

OS Implemented
iOS
Android

Checklist

  • I have tested this on a device and a simulator
  • I added the documentation in README.md
  • I updated the typed files (TS and Flow)
satya164
satya164

Could you please check this PR ASAP?

Can you not ping me on the weekend for a 5 hour old PR? If the PR is necessary for you then use patch-package to temporarily use it in your project.

push

satya164 push react-navigation/react-navigation.github.io

satya164
satya164

Deploy website - based on 193da95a69c7bf1de1c0ca4c0708686e3b129355

commit sha: ef1849d1597380182256cc86955c3690ce906486

push time in 1 month ago
Previous