Commit Graph

1210 Commits

Author SHA1 Message Date
Satyajit Sahoo
0e8fda3196 fix: handle back button in drawer itself 2020-01-31 01:53:50 +01:00
Satyajit Sahoo
9198597b7f fix: fix drawerType=back when drawer is on right
fixes #316
2020-01-31 01:40:28 +01:00
osdnk
9be904d9c4 fix: increase epsilon in CardContainer.tsx 2020-01-30 22:38:13 +01:00
Satyajit Sahoo
fa4a959549 fix: add warning when passing inline function to component prop 2020-01-30 05:03:32 +01:00
Satyajit Sahoo
d0510d0220 chore: tweak the album art example 2020-01-30 05:03:31 +01:00
Satyajit Sahoo
0b4bf1dcc8 refactor: drop unmountInactiveScreens in favor of unmountOnBlur… (#317)
The `unmountInactiveScreens` prop lets user unmount all inactive screens for the whole navigator when they go out of focus. It'll be better to have the option to do that per screen, so I have added the `unmountOnBlur` option instead.

To get the previous behaviour, user can specify the option in `screenOptions`.
2020-01-29 23:49:31 +01:00
Satyajit Sahoo
5a3f8356b0 feat: integrate with history API on web 2020-01-29 23:14:12 +01:00
Satyajit Sahoo
eeae11033a refactor: track history for tabs and drawer in a history key 2020-01-29 23:14:12 +01:00
Wojciech Lewicki
b931ae62df feat: add screens prop for nested configs (#308)
Nested configs' names with their configs are now in `screens` property of the route object.
2020-01-29 16:26:17 +01:00
Satyajit Sahoo
ea66b1a3b8 chore: fix build failure 2020-01-29 12:13:37 +01:00
Michał Osadnik
4bc0c8f66f feat: add error if multiple instances of useLinking are used (#310) 2020-01-29 11:35:22 +01:00
Satyajit Sahoo
68016de385 chore: add example for transparent card 2020-01-28 21:25:27 +01:00
Michał Osadnik
e55e866af2 feat: add deeplinking to native example (#309) 2020-01-28 16:47:01 +01:00
osdnk
50b366e734 fix: rtl in native app example 2020-01-28 15:40:08 +01:00
osdnk
edf96d839f fix: web with internal interpolation listener 2020-01-28 14:52:41 +01:00
Satyajit Sahoo
141d397bdf chore: tweak types for stack 2020-01-28 14:35:31 +01:00
Evan Bacon
0f18b91690 refactor: split Overlay into a new component (#284)
* refactor: split Overlay into a new component

* Update packages/drawer/src/index.tsx

Co-Authored-By: Satyajit Sahoo <satyajit.happy@gmail.com>

Co-authored-by: Satyajit Sahoo <satyajit.happy@gmail.com>
2020-01-27 20:10:06 +01:00
Satyajit Sahoo
6262f7298b feat: add animationTypeForReplace option (#297)
Currently, when a screen is replaced the new screen comes into focus with a push animation. However, sometimes you might want to customize how the animation looks like.

For example, when the user logs out, animating out the previous screen like pop feels more natural than doing a push animation with the sign in screen. The PR adds a new `animationTypeForReplace` option to control this. Specifying `animationTypeForReplace: 'pop'` will pop the previous screen, otherwise the new screen will be pushed like before.

Co-authored-by: Michał Osadnik <micosa97@gmail.com>
2020-01-27 18:20:53 +01:00
osdnk
a6f58677dc fix: make UNVERSIONED insufficient expo version 2020-01-27 18:01:35 +01:00
Michał Osadnik
9bfb295620 fix: screens integration on Android (#294) 2020-01-27 17:48:22 +01:00
Satyajit Sahoo
ecd68afb46 feat: add useIsDrawerOpen hook (#299) 2020-01-27 12:59:24 +01:00
Satyajit Sahoo
5fe140e61b fix: fix shadow position for inverted animations 2020-01-26 17:02:00 +01:00
Satyajit Sahoo
944fa35ed4 fix: throw when assigning or accessing the router property in compat 2020-01-26 02:22:16 +01:00
Satyajit Sahoo
2243b45cc1 fix: tweak error messages for validation 2020-01-25 14:42:17 +01:00
Satyajit Sahoo
5e7cfc4ac0 chore: publish
- @react-navigation/bottom-tabs@5.0.0-alpha.39
 - @react-navigation/compat@5.0.0-alpha.28
 - @react-navigation/core@5.0.0-alpha.37
 - @react-navigation/drawer@5.0.0-alpha.41
 - @react-navigation/material-bottom-tabs@5.0.0-alpha.36
 - @react-navigation/material-top-tabs@5.0.0-alpha.35
 - @react-navigation/native-stack@5.0.0-alpha.29
 - @react-navigation/native@5.0.0-alpha.29
 - @react-navigation/routers@5.0.0-alpha.27
 - @react-navigation/stack@5.0.0-alpha.63
@react-navigation/drawer@5.0.0-alpha.41 @react-navigation/material-top-tabs@5.0.0-alpha.35 @react-navigation/compat@5.0.0-alpha.28 @react-navigation/core@5.0.0-alpha.37 @react-navigation/stack@5.0.0-alpha.63 @react-navigation/material-bottom-tabs@5.0.0-alpha.36 @react-navigation/routers@5.0.0-alpha.27 @react-navigation/native@5.0.0-alpha.29 @react-navigation/native-stack@5.0.0-alpha.29 @react-navigation/bottom-tabs@5.0.0-alpha.39
2020-01-24 13:01:24 +01:00
NoemiRozpara
5751e7f97a fix: warn if non-serializable values found in state 2020-01-24 12:58:06 +01:00
Satyajit Sahoo
179e807a64 fix: add error message when trying to use v4 API with v5 2020-01-24 00:01:35 +01:00
Satyajit Sahoo
2f1f0af862 fix: validate screen configs 2020-01-23 23:52:27 +01:00
Satyajit Sahoo
9976a888a0 refactor: move replace to stack router 2020-01-23 20:13:40 +01:00
Satyajit Sahoo
16c64e7298 fix: pass correct previous scene to header with headerMode: screen 2020-01-23 15:29:40 +01:00
Satyajit Sahoo
f1fe951cf9 fix: use layout instead of dimensions for determining tab bar layout 2020-01-23 15:10:27 +01:00
Satyajit Sahoo
14250851d1 refactor: remove resetRoot from the navigation prop
Using `resetRoot` requires knowledge of the whole navigation tree that a specific screen shouldn't have. It's better to remove it to discourage resetting whole navigator state from inside a screen.

It's still possible if the user needs it:
- Expose `resetRoot` from container's ref via context
- Use `reset` with the target set to the root navigation state's key
2020-01-23 14:44:34 +01:00
osdnk
42586462fd chore: publish
- @react-navigation/bottom-tabs@5.0.0-alpha.38
 - @react-navigation/compat@5.0.0-alpha.27
 - @react-navigation/core@5.0.0-alpha.36
 - @react-navigation/drawer@5.0.0-alpha.40
 - @react-navigation/material-bottom-tabs@5.0.0-alpha.35
 - @react-navigation/material-top-tabs@5.0.0-alpha.34
 - @react-navigation/native-stack@5.0.0-alpha.28
 - @react-navigation/native@5.0.0-alpha.28
 - @react-navigation/routers@5.0.0-alpha.26
 - @react-navigation/stack@5.0.0-alpha.62
@react-navigation/native-stack@5.0.0-alpha.28 @react-navigation/native@5.0.0-alpha.28 @react-navigation/routers@5.0.0-alpha.26 @react-navigation/stack@5.0.0-alpha.62 @react-navigation/material-top-tabs@5.0.0-alpha.34 @react-navigation/drawer@5.0.0-alpha.40 @react-navigation/bottom-tabs@5.0.0-alpha.38 @react-navigation/compat@5.0.0-alpha.27 @react-navigation/core@5.0.0-alpha.36 @react-navigation/material-bottom-tabs@5.0.0-alpha.35
2020-01-23 10:45:49 +01:00
Satyajit Sahoo
3dede316cc feat: add preventDefault functionality in material bottom tabs 2020-01-22 21:57:39 +01:00
Satyajit Sahoo
63988e0da8 chore: add sideEffects: false for webpack 2020-01-22 21:47:12 +01:00
Satyajit Sahoo
67b2ecfcfc chore: update stack examples 2020-01-22 15:46:51 +01:00
Satyajit Sahoo
68ed8a7259 fix: handle popping more than available screens in stack 2020-01-22 00:33:50 +01:00
Satyajit Sahoo
6c2acbb304 fix: make sure that we return correct value if selector changes
https://github.com/react-navigation/navigation-ex/pull/273#issuecomment-576581225
2020-01-21 18:04:04 +01:00
Satyajit Sahoo
84d75b37e7 chore: add a toggle for RTL 2020-01-20 15:58:46 +01:00
Satyajit Sahoo
65e5147910 chore: add some more examples 2020-01-20 15:38:05 +01:00
Satyajit Sahoo
321fa653ad fix: handle header translation for horizontal-inverted
When going from a screen with header to screen with no header, we need to translate the header to right if the animation direction is inverted.
2020-01-20 10:55:10 +01:00
Satyajit Sahoo
2a76dc4d3c fix: improvements to the compat layer 2020-01-20 10:36:57 +01:00
Satyajit Sahoo
0a982ee698 fix: don't use native driver on web
The native driver is not supported for animations on web. It just prints a wanrning in the console. So we conditionally disable it on web.
2020-01-20 06:20:06 +01:00
Satyajit Sahoo
1da4a6437f fix: fix types for native stack 2020-01-20 05:39:08 +01:00
Satyajit Sahoo
f1df4a0808 feat: emit appear and dismiss events for native stack 2020-01-20 05:28:41 +01:00
Satyajit Sahoo
14ae3738cf fix: ensure re-render on isFirstRouteInParent change in compat layer 2020-01-19 03:44:16 +01:00
Satyajit Sahoo
32a2206513 feat: add useNavigationState hook
Sometimes it's useful to get the current navigation state inside a screen. We have the `dangerouslyGetState` method for that. However, the problem with this method is that it won't trigger a re-render when it changes, so user cannot rely on it for rendering something.

This adds a 2 things:
1. A `state` event similar to `focus` and `blur` that user can subscribe to
2. A `useNavigationState` hook that takes a selector and returns part of the state

Internally `useNavigationState` subscribes to the state event to get the current navigation state.

I have also made it mandatory to pass a selector to `useNavigationState`. This makes it harder to accidentally get the whole navigation state, which will trigger a re-render every time anything changes, even if we don't care about the change. With a selector, we can tell which part we care about, and if that part didn't change, it won't trigger a re-render.

For example, to get the same functionality as the old `isFirstRouteInParent` method:

```js
function MyComponent({ route }) {
  const isFirstRouteInParent = useNavigationState(state => state.routes[0] === route);

  // content
}
```
2020-01-18 23:25:42 +01:00
Satyajit Sahoo
38520a97ff fix: position inactivscreensws offscreen by default 2020-01-18 23:13:36 +01:00
Satyajit Sahoo
3bf5ddde2a fix: don't add ?if query params is empty 2020-01-18 22:30:39 +01:00
Satyajit Sahoo
43d2c456be fix: slide the header up to hide it for vertical animation 2020-01-18 04:13:37 +01:00