docs: update issue template

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,32 @@
+<!-- Issues that don't use this template are likely to be closed. -->
+<!-- Please search the existing issues and read the documentation before opening an issue. -->
+
+### Current behaviour
+
+<!-- What's currently happening? -->
+
+### Expected behaviour
+
+<!-- What do you expect to happen? If there is an error, provide the complete error message with stack trace. -->
+
+### Code sample
+
+<!-- Provide a complete code sample that could be run to reproduce the issue, ideally on snack.expo.io or in a github repo. -->
+
+### Screenshots (if applicable)
+
+<!-- Include screenshots if there's a bug in the layout. -->
+
+### What have you tried
+
+<!-- List down the steps you have tried to fix or identify the issue and links to any related issues you found. -->
+
+### Your Environment
+
+| software              | version
+| --------------------- | -------
+| ios or android        |
+| react-native          |
+| react-native-tab-view |
+| node                  |
+| npm or yarn           |

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,10 @@
+<!-- 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. -->

README.md

@@ -206,7 +206,7 @@ renderScene = SceneMap({
 Each scene receives the following props:
 
 - `route` - the current route rendered by the component
-- `jumpTo` - method to jump to other tabs, it receives `route.key` as it's argument
+- `jumpTo` - method to jump to other tabs, takes a `route.key` as it's argument
 
 All the scenes rendered with `SceneMap` are optimized using `React.PureComponent` and don't re-render when parent's props or states change. If you don't want this behaviour, or want to pass additional props to your scene components, use `renderScene` directly instead of using `SceneMap`.
 

example/app.json

@@ -7,9 +7,9 @@
     "version": "1.0.0",
     "orientation": "portrait",
     "primaryColor": "#2196f3",
-    "icon": "https://s3.amazonaws.com/exp-us-standard/icons/react-native-tab-view-icon.png",
+    "icon": "assets/icon.png",
     "loading": {
-      "icon": "https://s3.amazonaws.com/exp-us-standard/icons/react-native-tab-view-icon.png",
+      "icon": "assets/icon.png",
       "hideExponentText": false
     },
     "packagerOpts": {

src/TabViewPagerAndroid.web.js

@@ -1,12 +1,6 @@
 import React from 'react';
-import { Text } from 'react-native';
 
-export default class TabViewPagerAndroid<T: *> extends React.Component<
-  Props<T>
-> {
-  render() {
-    return (
-      <Text>The TabViewPagerAndroid is not supported on React Native Web</Text>
-    );
-  }
+// This component is a stub to support React Native web
+export default function TabViewPagerAndroid() {
+  return <p>TabViewPagerAndroid is not supported on web.</p>;
 }