* Revert "Workaround nested TabNavigation swipe issue (#2733)"
This reverts commit 7b88a475bc283ce01fc9b6d57d0c28f4b34879d0.
* Set initialLayout in defaultProps on Android
This reverts the previous PR (#2733) and takes into account #2385
In order to fix https://github.com/react-native-community/react-native-tab-view/issues/312
* Don't use window's dimensions
* Fix animation (#1493)
* Rewrite the file animatedInterpolate.js. To increase readability.
* Rename the variable, To increase readability.
* minor renaming
* Pass transition and modal props to transitionConfigurer
* Make arguments passed to transitionConfigurer required
* Update docs with params passed to transitionConfigurer
* Give docs some more room to breath
* Working on the new docs
* New intro
* Writing installation guide
* Finish tab intro.
* Write intro to drawernavigator.
* Add some space
* Rename guide
* Minimize changes
* Fix links
* Edits
* Fixes default drawerWidth to match material ui patterns.
Previously: calculated based on device width regardless of orientation and did not recalculate when orientation changed.
Now: calculates based on minimum of device height/width, remains constant and guaranteed to always fit screen regardless of orientation.
This is the expected behavior based on observing Google apps (e.g. Gmail). This is also better than recalculating on every orientation change, which would result in variable width drawers and awkward empty space when in landscape in most cases.
* Remove console.log
* Handle the ios11 tabbar correctly
* Fix an issue when showLabel is false
* Add a basic test for the tabbarbottom
* Add check for ios version number
* Tests shall pass
* make things work for all the versions
* Again, fix the tests
* added property inside drawerConfig to backgroundColor (drawerBackgroundColor)
* Adjusting documentation for PR deployment (# 2698)
* add example in the doc
* fix issue #2251 by including queryString to get nested action
* only use nested query string when original queryString exists, and include test cases
* Fixing Intro Guide
Fixes#832 - the code in this page was wrong, that export default was causing errors.
I've also modified a few phrases here and there to help the comprehension.
* more fixes, for CRNA
the problem I see with many bug reports in this repo is that people write a very vague description of what their problem is and expect to get some help. I tried to:
1 . emphasise how important it is to include a runnable reproduction
2 . cut down on some extra words at the beginning of the template so it's more to the point