reverting accidental IDE merge of Pressable doc--it's still in review

Simek · May 14, 2020 · cca0b83 · cca0b83
1 parent 4b93c2b
commit cca0b83
Show file tree

Hide file tree

Showing 6 changed files with 0 additions and 12 deletions.
diff --git a/docs/touchablehighlight.md b/docs/touchablehighlight.md
@@ -3,8 +3,6 @@ id: touchablehighlight
 title: TouchableHighlight
 ---
 
-> If you're looking for a more extensive and future-proof way to handle touch-based input, check out the [Pressable](pressable.md) API.
-
 A wrapper for making views respond properly to touches. On press down, the opacity of the wrapped view is decreased, which allows the underlay color to show through, darkening or tinting the view.
 
 The underlay comes from wrapping the child in a new View, which can affect layout, and sometimes cause unwanted visual artifacts if not used correctly, for example if the backgroundColor of the wrapped view isn't explicitly set to an opaque color.

diff --git a/docs/touchablenativefeedback.md b/docs/touchablenativefeedback.md
@@ -3,8 +3,6 @@ id: touchablenativefeedback
 title: TouchableNativeFeedback
 ---
 
-> If you're looking for a more extensive and future-proof way to handle touch-based input, check out the [Pressable](pressable.md) API.
-
 A wrapper for making views respond properly to touches (Android only). On Android this component uses native state drawable to display touch feedback.
 
 At the moment it only supports having a single View instance as a child node, as it's implemented by replacing that View with another instance of RCTView node with some additional properties set.

diff --git a/docs/touchableopacity.md b/docs/touchableopacity.md
@@ -3,8 +3,6 @@ id: touchableopacity
 title: TouchableOpacity
 ---
 
-> If you're looking for a more extensive and future-proof way to handle touch-based input, check out the [Pressable](pressable.md) API.
-
 A wrapper for making views respond properly to touches. On press down, the opacity of the wrapped view is decreased, dimming it.
 
 Opacity is controlled by wrapping the children in an `Animated.View`, which is added to the view hierarchy. Be aware that this can affect layout.

diff --git a/docs/touchablewithoutfeedback.md b/docs/touchablewithoutfeedback.md
@@ -3,8 +3,6 @@ id: touchablewithoutfeedback
 title: TouchableWithoutFeedback
 ---
 
-> If you're looking for a more extensive and future-proof way to handle touch-based input, check out the [Pressable](pressable.md) API.
-
 Do not use unless you have a very good reason. All elements that respond to press should have a visual feedback when touched.
 
 `TouchableWithoutFeedback` supports only one child. If you wish to have several child components, wrap them in a View. Importantly, `TouchableWithoutFeedback` works by cloning its child and applying responder props to it. It is therefore required that any intermediary components pass through those props to the underlying React Native component.

diff --git a/website/i18n/en.json b/website/i18n/en.json
@@ -266,9 +266,6 @@
       "platformcolor": {
         "title": "PlatformColor"
       },
-      "pressable": {
-        "title": "Pressable"
-      },
       "profiling": {
         "title": "Profiling"
       },

diff --git a/website/sidebars.json b/website/sidebars.json
@@ -72,7 +72,6 @@
       "imagebackground",
       "keyboardavoidingview",
       "modal",
-      "pressable",
       "refreshcontrol",
       "safeareaview",
       "scrollview",