I've noticed that link to the _getting started_ page in the docs seems to not working as expected since `*.html` extension is added anyway and it makes the link broken:
`https://callstack.github.io/react-native-paper/getting-started.html.html`.
### Motivation
The documentation is important part of the library and should be working properly.
### Test plan
Enter `/docs`, install using `yarn` and run it with `yarn start`.
> **NOTE:** _the current version works on localhost and breaks only in the prod env. Suggested change will probably work in both, but needs to be verified by someone who knows the deployment process._
### Motivation
Update documentation with new version `2.0.1` of `react-native-paper`. RadioButton props are quite different from version 1 to 2, so docs needed an update.
### Test plan
See docs.
reference: https://github.com/wix/react-native-navigation/issues/2892
in short, javascript A && B syntax will return A if A is false. if A is empty string, it will return empty string (which is false if evaluated as boolean) this most of the time works but not here. {A && `<Text>sth</Text>`}, will return "" when A is empty string. This have no problem in iPhone, but returning an empty string to rn component other that` <Text> `will crash in android. The fatal error message can only be viewed using android device monitor or logcat, no message will show in console (as it is a flash crash).
To reproduce, put an empty string in subtitle. the double !! first turn empty string '' to true and then false. return false or null is save within JSX
07-26 21:07:41.735: E/AndroidRuntime(16154): java.lang.RuntimeException: abi26_0_0.com.facebook.react.uimanager.IllegalViewOperationException: Trying to add unknown view tag: 1472
07-26 21:07:41.735: E/AndroidRuntime(16154): detail: View tag:1479
07-26 21:07:41.735: E/AndroidRuntime(16154): children(2): [
07-26 21:07:41.735: E/AndroidRuntime(16154): 1468,1470,
07-26 21:07:41.735: E/AndroidRuntime(16154): ],
07-26 21:07:41.735: E/AndroidRuntime(16154): viewsToAdd(1): [
07-26 21:07:41.735: E/AndroidRuntime(16154): [2,1472],
07-26 21:07:41.735: E/AndroidRuntime(16154): ],
07-26 21:07:41.735: E/AndroidRuntime(16154): at abi26_0_0.com.facebook.react.bridge.ReactContext.handleException(ReactContext.java:313)
07-26 21:07:41.735: E/AndroidRuntime(16154): at abi26_0_0.com.facebook.react.uimanager.GuardedFrameCallback.doFrame(GuardedFrameCallback.java:33)
<!-- Please provide enough information so that others can review your pull request. -->
<!-- Keep pull requests small and focused on a single change. -->
### Motivation
<!-- What existing problem does the pull request solve? Can you solve the issue with a different approach? -->
### Test plan
<!-- List the steps with which we can test this change. Provide screenshots if this changes anything visual. -->
I had the same issue described in #477 where I need to pass testID and/or accessibilityLabel to buttons to find them in e2e tests.
The same behaviour is implemented in other components such as [FAB](https://github.com/callstack/react-native-paper/blob/master/src/components/FAB.js#L97)
Create a button and pass a testID
```
function testID(id) {
return Platform.OS === 'android' ? { accessible: true, accessibilityLabel: id } : { testID: id }
}
<Button
{...testID('skip-button')}
onPress={async () => {
// ...
}}
>
Skip
</Button>
```
This works now in appium tests with wd
```
const skipButton = await client.elementByAccessibilityId('skip-button')
await skipButton.click()
```
<!-- Please provide enough information so that others can review your pull request. -->
<!-- Keep pull requests small and focused on a single change. -->
### Motivation
<!-- What existing problem does the pull request solve? Can you solve the issue with a different approach? -->
### Test plan
<!-- List the steps with which we can test this change. Provide screenshots if this changes anything visual. -->
Since #491 the content is not centered automatically anymore because the children take up 100% and `justifyContent` on the parent container has no effect.
