Feature Requests

## Problem Currently, the safeAreaInsets option in BottomTabView only accepts a static object. This causes issues on Android when users switch navigation modes (e.g., between gesture navigation and button navigation), as the safe area values cannot be updated dynamically to reflect the current navigation mode. ## Proposed Solution Allow safeAreaInsets to accept a function that receives the current insets from SafeAreaInsetsContext as a parameter, enabling dynamic safe area calculations. ## Implementation Example BottomTabView.tsx : const renderTabBar = () => { return ( <SafeAreaInsetsContext.Consumer> {(insets) => tabBar({ state: state, descriptors: descriptors, navigation: navigation, insets: { top: safeAreaInsets?.(insets)?.top ?? insets?.top ?? 0, right: safeAreaInsets?.(insets)?.right ?? insets?.right ?? 0, bottom: safeAreaInsets?.(insets)?.bottom ?? insets?.bottom ?? 0, left: safeAreaInsets?.(insets)?.left ?? insets?.left ?? 0, }, }) } </SafeAreaInsetsContext.Consumer> ); }; ## Usage in options: safeAreaInsets: (insets) => { if (insets) { return { bottom: insets.bottom + 8, }; } return { bottom: SafeAreaProviderCompat.initialMetrics.insets.bottom + 8, }; } ## Benefits Dynamically adjusts safe area insets based on current device configuration Resolves Android navigation mode switching issues Maintains backward compatibility (can still accept static object) Provides more flexibility for custom safe area adjustments

Right now in the current options that exist are regular | medium | bold | heavy it would be nice to have the full spectrum that TextStyle['fontWeight'] has being e.g. black | ultralight | 'light' | 'thin' | etc... As I find it odd if I specify a named option that doesnt exist in the navigation theme (e.g. black not 900 ) it will not work.

A simple way is to list my current @react-navigation packages along with their installed versions. This helps me identify the versions I can update. For example, if I'm on v6, I list all my @react-navigation packages, and the website can help me determine which dependencies or packages are needed to update or migrate to v7. For instance, I can check if I need react-native-screens v4.5.0 with v7 or if I can keep my current version, etc.

as per beginner level, whenever i need something, i just come to navigation website and search about it, so according my need i got so many options , props, properties, but i cant able to clear about which property what to do. so my request is, can you make one preview section for all properties , so we can easily see effect of that property, right now, we have to read description for that properties. check react native website , you can easily catch my point, whats i am requesting. or i attached some screenshots, you can refer that also, two ss from react native website and one from react navigation website.

Is native iOS scale-down animation supported when presenting modals with formSheet presentation style in React Native Navigation ?

the routes can have an loader prop, a function that receives the routes params and can return a promise. This promise can be consumed in the Routes component with a useLoader prop. There is also a way to rerun the loader . A loadingComponent prop implements the loading state. Bonus: throwing special errors in the loader , for example redirect('..', { withAnimation: boolean })

Is there any way to know the progress of the current depth? For example, If we go from 0 to 1, 0.1, 0.2, 0.3, ..., 1 If we go from 1 to 2, 1.1, 1.2, 1.3, ..., 2 If we go from 2 to 1 again, 1.9, 1.8, 1.7, ..., 1 Is there any way to get this?

Is there any way to know the progress of the current depth? For example, If we go from 0 to 1, 0.1, 0.2, 0.3, ..., 1 If we go from 1 to 2, 1.1, 1.2, 1.3, ..., 2 If we go from 2 to 1 again, 1.9, 1.8, 1.7, ..., 1 Is there any way to get this?

We would like to build a separate animation on transition between react-native-pager-view Pages. If we're using tab-view, we have access to onSwipeStart and onSwipeEnd callbacks. I can see that PagerView has an onPageScroll, which would allow us to set up a shared value on this transition between pages. Would it be simple to expose this prop also over tab-view?