Skip to content

Fix MDX double <p> tags#4267

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Simek merged 1 commit into from
Oct 10, 2024
Merged

Fix MDX double <p> tags #4267

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 1 addition & 3 deletions docs/appregistry.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: AppRegistry

<div className="banner-native-code-required">
<h3>Project with Native Code Required</h3>
<p>
If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.
</p>
<p>If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.</p>
</div>

`AppRegistry` is the JS entry point to running all React Native apps. App root components should register themselves with `AppRegistry.registerComponent`, then the native system can load the bundle for the app and then actually run the app when it's ready by invoking `AppRegistry.runApplication`.
Expand Down
4 changes: 1 addition & 3 deletions docs/debugging-native-code.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import con

<div className="banner-native-code-required">
<h3>Projects with Native Code Only</h3>
<p>
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.
</p>
<p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.</p>
</div>

## Accessing Logs
Expand Down
4 changes: 1 addition & 3 deletions docs/linking.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -30,9 +30,7 @@ As mentioned in the introduction, there are some URL schemes for core functional

<div className="banner-native-code-required">
<h3>Projects with Native Code Only</h3>
<p>
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.
</p>
<p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.</p>
</div>

If you want to enable deep links in your app, please read the below guide:
Expand Down
4 changes: 1 addition & 3 deletions docs/permissionsandroid.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: PermissionsAndroid

<div className="banner-native-code-required">
<h3>Project with Native Code Required</h3>
<p>
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.
</p>
<p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.</p>
</div>

`PermissionsAndroid` provides access to Android M's new permissions model. The so-called "normal" permissions are granted by default when the application is installed as long as they appear in `AndroidManifest.xml`. However, "dangerous" permissions require a dialog prompt. You should use this module for those permissions.
Expand Down
4 changes: 1 addition & 3 deletions docs/pushnotificationios.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ title: '🚧 PushNotificationIOS'

<div className="banner-native-code-required">
<h3>Projects with Native Code Only</h3>
<p>
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.
</p>
<p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.</p>
</div>

Handle notifications for your app, including scheduling and permissions.
Expand Down
18 changes: 4 additions & 14 deletions website/blog/2020-07-06-version-0.63.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -61,9 +61,7 @@ import {Pressable, Text} from 'react-native';
</Pressable>;
```

<p className="snippet-caption">
A simple example of a Pressable component in action
</p>
<p className="snippet-caption">A simple example of a Pressable component in action</p>

You can learn more about it from [the documentation](https://reactnative.dev/docs/pressable).

Expand All@@ -85,10 +83,7 @@ import {Text, PlatformColor} from 'react-native';
</Text>;
```

<p className="snippet-caption">
Sets the color of the Text component to labelColor as defined by
iOS.
</p>
<p className="snippet-caption">Sets the color of the Text component to labelColor as defined by iOS.</p>

Android, on the other hand, [provides colors like colorButtonNormal](https://developer.android.com/reference/android/R.attr#colorButtonNormal). You can use this color in React Native with:

Expand All@@ -103,10 +98,7 @@ import {View, Text, PlatformColor} from 'react-native';
</View>;
```

<p className="snippet-caption">
Sets the background color of the View component to
colorButtonNormal as defined by Android.
</p>
<p className="snippet-caption">Sets the background color of the View component to colorButtonNormal as defined by Android.</p>

You can learn more about `PlatformColor` from [the documentation](https://reactnative.dev/docs/platformcolor). You can also check the actual [code examples present in the RNTester](https://github.com/facebook/react-native/blob/master/packages/rn-tester/js/examples/PlatformColor/PlatformColorExample.js).

Expand All@@ -125,9 +117,7 @@ const customDynamicTextColor = DynamicColorIOS({
</Text>;
```

<p className="snippet-caption">
Changes the text color based on the system theme
</p>
<p className="snippet-caption">Changes the text color based on the system theme</p>

You can learn more about `DynamicColorIOS` from [the documentation](https://reactnative.dev/docs/dynamiccolorios).

Expand Down
4 changes: 1 addition & 3 deletions website/versioned_docs/version-0.70/appregistry.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: AppRegistry

<div className="banner-native-code-required">
<h3>Project with Native Code Required</h3>
<p>
If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.
</p>
<p>If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.</p>
</div>

`AppRegistry` is the JS entry point to running all React Native apps. App root components should register themselves with `AppRegistry.registerComponent`, then the native system can load the bundle for the app and then actually run the app when it's ready by invoking `AppRegistry.runApplication`.
Expand Down
6 changes: 2 additions & 4 deletions website/versioned_docs/version-0.70/debugging.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -164,10 +164,8 @@ You can view installation instructions [in the README](https://github.com/infini
# Native Debugging

<div className="banner-native-code-required">
<h3>Projects with Native Code Only</h3>
<p>
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.
</p>
<h3>Projects with Native Code Only</h3><p>
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.</p>
</div>

## Accessing console logs
Expand Down
4 changes: 1 addition & 3 deletions website/versioned_docs/version-0.70/linking.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -30,9 +30,7 @@ As mentioned in the introduction, there are some URL schemes for core functional

<div className="banner-native-code-required">
<h3>Projects with Native Code Only</h3>
<p>
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.
</p>
<p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.</p>
</div>

If you want to enable deep links in your app, please read the below guide:
Expand Down
4 changes: 1 addition & 3 deletions website/versioned_docs/version-0.70/permissionsandroid.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import con

<div className="banner-native-code-required">
<h3>Project with Native Code Required</h3>
<p>
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.
</p>
<p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.</p>
</div>

`PermissionsAndroid` provides access to Android M's new permissions model. The so-called "normal" permissions are granted by default when the application is installed as long as they appear in `AndroidManifest.xml`. However, "dangerous" permissions require a dialog prompt. You should use this module for those permissions.
Expand Down
4 changes: 1 addition & 3 deletions website/versioned_docs/version-0.70/pushnotificationios.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ title: '🚧 PushNotificationIOS'

<div className="banner-native-code-required">
<h3>Projects with Native Code Only</h3>
<p>
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.
</p>
<p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.</p>
</div>

Handle push notifications for your app, including permission handling and icon badge number.
Expand Down
4 changes: 1 addition & 3 deletions website/versioned_docs/version-0.71/appregistry.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: AppRegistry

<div className="banner-native-code-required">
<h3>Project with Native Code Required</h3>
<p>
If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.
</p>
<p>If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.</p>
</div>

`AppRegistry` is the JS entry point to running all React Native apps. App root components should register themselves with `AppRegistry.registerComponent`, then the native system can load the bundle for the app and then actually run the app when it's ready by invoking `AppRegistry.runApplication`.
Expand Down
6 changes: 2 additions & 4 deletions website/versioned_docs/version-0.71/debugging.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -164,10 +164,8 @@ You can view installation instructions [in the README](https://github.com/infini
# Native Debugging

<div className="banner-native-code-required">
<h3>Projects with Native Code Only</h3>
<p>
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.
</p>
<h3>Projects with Native Code Only</h3><p>
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.</p>
</div>

## Accessing console logs
Expand Down
4 changes: 1 addition & 3 deletions website/versioned_docs/version-0.71/linking.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -30,9 +30,7 @@ As mentioned in the introduction, there are some URL schemes for core functional

<div className="banner-native-code-required">
<h3>Projects with Native Code Only</h3>
<p>
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.
</p>
<p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.</p>
</div>

If you want to enable deep links in your app, please read the below guide:
Expand Down
4 changes: 1 addition & 3 deletions website/versioned_docs/version-0.71/permissionsandroid.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import con

<div className="banner-native-code-required">
<h3>Project with Native Code Required</h3>
<p>
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.
</p>
<p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.</p>
</div>

`PermissionsAndroid` provides access to Android M's new permissions model. The so-called "normal" permissions are granted by default when the application is installed as long as they appear in `AndroidManifest.xml`. However, "dangerous" permissions require a dialog prompt. You should use this module for those permissions.
Expand Down
4 changes: 1 addition & 3 deletions website/versioned_docs/version-0.71/pushnotificationios.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ title: '🚧 PushNotificationIOS'

<div className="banner-native-code-required">
<h3>Projects with Native Code Only</h3>
<p>
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.
</p>
<p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.</p>
</div>

Handle push notifications for your app, including permission handling and icon badge number.
Expand Down
4 changes: 1 addition & 3 deletions website/versioned_docs/version-0.72/appregistry.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: AppRegistry

<div className="banner-native-code-required">
<h3>Project with Native Code Required</h3>
<p>
If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.
</p>
<p>If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.</p>
</div>

`AppRegistry` is the JS entry point to running all React Native apps. App root components should register themselves with `AppRegistry.registerComponent`, then the native system can load the bundle for the app and then actually run the app when it's ready by invoking `AppRegistry.runApplication`.
Expand Down
4 changes: 1 addition & 3 deletions website/versioned_docs/version-0.72/linking.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -30,9 +30,7 @@ As mentioned in the introduction, there are some URL schemes for core functional

<div className="banner-native-code-required">
<h3>Projects with Native Code Only</h3>
<p>
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.
</p>
<p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.</p>
</div>

If you want to enable deep links in your app, please read the below guide:
Expand Down
6 changes: 2 additions & 4 deletions website/versioned_docs/version-0.72/native-debugging.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -6,10 +6,8 @@ title: Native Debugging
import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import constants from '@site/core/TabsConstants';

<div className="banner-native-code-required">
<h3>Projects with Native Code Only</h3>
<p>
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.
</p>
<h3>Projects with Native Code Only</h3><p>
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.</p>
</div>

## Accessing native logs
Expand Down
4 changes: 1 addition & 3 deletions website/versioned_docs/version-0.72/permissionsandroid.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: PermissionsAndroid

<div className="banner-native-code-required">
<h3>Project with Native Code Required</h3>
<p>
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.
</p>
<p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.</p>
</div>

`PermissionsAndroid` provides access to Android M's new permissions model. The so-called "normal" permissions are granted by default when the application is installed as long as they appear in `AndroidManifest.xml`. However, "dangerous" permissions require a dialog prompt. You should use this module for those permissions.
Expand Down
4 changes: 1 addition & 3 deletions website/versioned_docs/version-0.72/pushnotificationios.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ title: '🚧 PushNotificationIOS'

<div className="banner-native-code-required">
<h3>Projects with Native Code Only</h3>
<p>
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.
</p>
<p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.</p>
</div>

Handle push notifications for your app, including permission handling and icon badge number.
Expand Down
Loading
, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all 
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Fix MDX double `<p>` tags by slorber · Pull Request #4267 · react/react-native-website · GitHub
Skip to content
Fix MDX double <p> tags#4267

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

 Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

 Merged

Simek
merged 1 commit into

from

Oct 10, 2024
 Merged


Fix MDX double <p> tags
#4267
Show file tree
Hide file tree
 Changes from all commits
Commits

Show all changes


1 commit


Select commit


File filter

Filter by extension
Filter by extension
Conversations

Failed to load comments. 
Loading
Jump to

Jump to file


Failed to load files. 
Loading
 Diff view

 Diff view


4 changes: 1 addition & 3 deletions
docs/appregistry.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: AppRegistry

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.
 </p>
 <p>If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.</p>
</div>

`AppRegistry` is the JS entry point to running all React Native apps. App root components should register themselves with `AppRegistry.registerComponent`, then the native system can load the bundle for the app and then actually run the app when it's ready by invoking `AppRegistry.runApplication`.
Expand Down

4 changes: 1 addition & 3 deletions
docs/debugging-native-code.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import con

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.</p>
</div>

## Accessing Logs
Expand Down

4 changes: 1 addition & 3 deletions
docs/linking.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -30,9 +30,7 @@ As mentioned in the introduction, there are some URL schemes for core functional

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.</p>
</div>

If you want to enable deep links in your app, please read the below guide:
Expand Down

4 changes: 1 addition & 3 deletions
docs/permissionsandroid.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: PermissionsAndroid

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.</p>
</div>

`PermissionsAndroid` provides access to Android M's new permissions model. The so-called "normal" permissions are granted by default when the application is installed as long as they appear in `AndroidManifest.xml`. However, "dangerous" permissions require a dialog prompt. You should use this module for those permissions.
Expand Down

4 changes: 1 addition & 3 deletions
docs/pushnotificationios.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ title: '🚧 PushNotificationIOS'

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.</p>
</div>

Handle notifications for your app, including scheduling and permissions.
Expand Down

18 changes: 4 additions & 14 deletions
website/blog/2020-07-06-version-0.63.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -61,9 +61,7 @@ import {Pressable, Text} from 'react-native';
</Pressable>;
```

<p className="snippet-caption">
 A simple example of a Pressable component in action
</p>
<p className="snippet-caption">A simple example of a Pressable component in action</p>

You can learn more about it from [the documentation](https://reactnative.dev/docs/pressable).

Expand All@@ -85,10 +83,7 @@ import {Text, PlatformColor} from 'react-native';
</Text>;
```

<p className="snippet-caption">
 Sets the color of the Text component to labelColor as defined by
 iOS.
</p>
<p className="snippet-caption">Sets the color of the Text component to labelColor as defined by iOS.</p>

Android, on the other hand, [provides colors like colorButtonNormal](https://developer.android.com/reference/android/R.attr#colorButtonNormal). You can use this color in React Native with:

Expand All@@ -103,10 +98,7 @@ import {View, Text, PlatformColor} from 'react-native';
</View>;
```

<p className="snippet-caption">
 Sets the background color of the View component to
 colorButtonNormal as defined by Android.
</p>
<p className="snippet-caption">Sets the background color of the View component to colorButtonNormal as defined by Android.</p>

You can learn more about `PlatformColor` from [the documentation](https://reactnative.dev/docs/platformcolor). You can also check the actual [code examples present in the RNTester](https://github.com/facebook/react-native/blob/master/packages/rn-tester/js/examples/PlatformColor/PlatformColorExample.js).

Expand All@@ -125,9 +117,7 @@ const customDynamicTextColor = DynamicColorIOS({
</Text>;
```

<p className="snippet-caption">
 Changes the text color based on the system theme
</p>
<p className="snippet-caption">Changes the text color based on the system theme</p>

You can learn more about `DynamicColorIOS` from [the documentation](https://reactnative.dev/docs/dynamiccolorios).

Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.70/appregistry.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: AppRegistry

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.
 </p>
 <p>If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.</p>
</div>

`AppRegistry` is the JS entry point to running all React Native apps. App root components should register themselves with `AppRegistry.registerComponent`, then the native system can load the bundle for the app and then actually run the app when it's ready by invoking `AppRegistry.runApplication`.
Expand Down

6 changes: 2 additions & 4 deletions
website/versioned_docs/version-0.70/debugging.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -164,10 +164,8 @@ You can view installation instructions [in the README](https://github.com/infini
# Native Debugging

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.
 </p>
 <h3>Projects with Native Code Only</h3><p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.</p>
</div>

## Accessing console logs
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.70/linking.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -30,9 +30,7 @@ As mentioned in the introduction, there are some URL schemes for core functional

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.</p>
</div>

If you want to enable deep links in your app, please read the below guide:
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.70/permissionsandroid.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import con

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.</p>
</div>

`PermissionsAndroid` provides access to Android M's new permissions model. The so-called "normal" permissions are granted by default when the application is installed as long as they appear in `AndroidManifest.xml`. However, "dangerous" permissions require a dialog prompt. You should use this module for those permissions.
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.70/pushnotificationios.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ title: '🚧 PushNotificationIOS'

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.</p>
</div>

Handle push notifications for your app, including permission handling and icon badge number.
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.71/appregistry.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: AppRegistry

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.
 </p>
 <p>If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.</p>
</div>

`AppRegistry` is the JS entry point to running all React Native apps. App root components should register themselves with `AppRegistry.registerComponent`, then the native system can load the bundle for the app and then actually run the app when it's ready by invoking `AppRegistry.runApplication`.
Expand Down

6 changes: 2 additions & 4 deletions
website/versioned_docs/version-0.71/debugging.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -164,10 +164,8 @@ You can view installation instructions [in the README](https://github.com/infini
# Native Debugging

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.
 </p>
 <h3>Projects with Native Code Only</h3><p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.</p>
</div>

## Accessing console logs
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.71/linking.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -30,9 +30,7 @@ As mentioned in the introduction, there are some URL schemes for core functional

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.</p>
</div>

If you want to enable deep links in your app, please read the below guide:
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.71/permissionsandroid.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import con

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.</p>
</div>

`PermissionsAndroid` provides access to Android M's new permissions model. The so-called "normal" permissions are granted by default when the application is installed as long as they appear in `AndroidManifest.xml`. However, "dangerous" permissions require a dialog prompt. You should use this module for those permissions.
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.71/pushnotificationios.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ title: '🚧 PushNotificationIOS'

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.</p>
</div>

Handle push notifications for your app, including permission handling and icon badge number.
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.72/appregistry.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: AppRegistry

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.
 </p>
 <p>If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.</p>
</div>

`AppRegistry` is the JS entry point to running all React Native apps. App root components should register themselves with `AppRegistry.registerComponent`, then the native system can load the bundle for the app and then actually run the app when it's ready by invoking `AppRegistry.runApplication`.
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.72/linking.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -30,9 +30,7 @@ As mentioned in the introduction, there are some URL schemes for core functional

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.</p>
</div>

If you want to enable deep links in your app, please read the below guide:
Expand Down

6 changes: 2 additions & 4 deletions
website/versioned_docs/version-0.72/native-debugging.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -6,10 +6,8 @@ title: Native Debugging
import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import constants from '@site/core/TabsConstants';

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.
 </p>
 <h3>Projects with Native Code Only</h3><p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.</p>
</div>

## Accessing native logs
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.72/permissionsandroid.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: PermissionsAndroid

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.</p>
</div>

`PermissionsAndroid` provides access to Android M's new permissions model. The so-called "normal" permissions are granted by default when the application is installed as long as they appear in `AndroidManifest.xml`. However, "dangerous" permissions require a dialog prompt. You should use this module for those permissions.
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.72/pushnotificationios.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ title: '🚧 PushNotificationIOS'

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.</p>
</div>

Handle push notifications for your app, including permission handling and icon badge number.
Expand Down
Loading

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Force GitHub README to respect dark mode
(function() {
var style = document.createElement('style');
style.textContent = '
.markdown-body {
color-scheme: dark light;
}
.markdown-body pre { background: #161b22 !important; }
.markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }
.markdown-body table th, .markdown-body table td { border-color: #30363d !important; }
.markdown-body img { background: #0d1117; }
.markdown-body blockquote { border-left-color: #8b949e; }
.markdown-body hr { border-color: #30363d; }
';
document.head.appendChild(style);
})();
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
Fix MDX double `<p>` tags by slorber · Pull Request #4267 · react/react-native-website · GitHub
Skip to content
Fix MDX double <p> tags#4267

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

 Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

 Merged

Simek
merged 1 commit into

from

Oct 10, 2024
 Merged


Fix MDX double <p> tags
#4267
Show file tree
Hide file tree
 Changes from all commits
Commits

Show all changes


1 commit


Select commit


File filter

Filter by extension
Filter by extension
Conversations

Failed to load comments. 
Loading
Jump to

Jump to file


Failed to load files. 
Loading
 Diff view

 Diff view


4 changes: 1 addition & 3 deletions
docs/appregistry.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: AppRegistry

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.
 </p>
 <p>If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.</p>
</div>

`AppRegistry` is the JS entry point to running all React Native apps. App root components should register themselves with `AppRegistry.registerComponent`, then the native system can load the bundle for the app and then actually run the app when it's ready by invoking `AppRegistry.runApplication`.
Expand Down

4 changes: 1 addition & 3 deletions
docs/debugging-native-code.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import con

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.</p>
</div>

## Accessing Logs
Expand Down

4 changes: 1 addition & 3 deletions
docs/linking.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -30,9 +30,7 @@ As mentioned in the introduction, there are some URL schemes for core functional

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.</p>
</div>

If you want to enable deep links in your app, please read the below guide:
Expand Down

4 changes: 1 addition & 3 deletions
docs/permissionsandroid.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: PermissionsAndroid

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.</p>
</div>

`PermissionsAndroid` provides access to Android M's new permissions model. The so-called "normal" permissions are granted by default when the application is installed as long as they appear in `AndroidManifest.xml`. However, "dangerous" permissions require a dialog prompt. You should use this module for those permissions.
Expand Down

4 changes: 1 addition & 3 deletions
docs/pushnotificationios.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ title: '🚧 PushNotificationIOS'

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.</p>
</div>

Handle notifications for your app, including scheduling and permissions.
Expand Down

18 changes: 4 additions & 14 deletions
website/blog/2020-07-06-version-0.63.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -61,9 +61,7 @@ import {Pressable, Text} from 'react-native';
</Pressable>;
```

<p className="snippet-caption">
 A simple example of a Pressable component in action
</p>
<p className="snippet-caption">A simple example of a Pressable component in action</p>

You can learn more about it from [the documentation](https://reactnative.dev/docs/pressable).

Expand All@@ -85,10 +83,7 @@ import {Text, PlatformColor} from 'react-native';
</Text>;
```

<p className="snippet-caption">
 Sets the color of the Text component to labelColor as defined by
 iOS.
</p>
<p className="snippet-caption">Sets the color of the Text component to labelColor as defined by iOS.</p>

Android, on the other hand, [provides colors like colorButtonNormal](https://developer.android.com/reference/android/R.attr#colorButtonNormal). You can use this color in React Native with:

Expand All@@ -103,10 +98,7 @@ import {View, Text, PlatformColor} from 'react-native';
</View>;
```

<p className="snippet-caption">
 Sets the background color of the View component to
 colorButtonNormal as defined by Android.
</p>
<p className="snippet-caption">Sets the background color of the View component to colorButtonNormal as defined by Android.</p>

You can learn more about `PlatformColor` from [the documentation](https://reactnative.dev/docs/platformcolor). You can also check the actual [code examples present in the RNTester](https://github.com/facebook/react-native/blob/master/packages/rn-tester/js/examples/PlatformColor/PlatformColorExample.js).

Expand All@@ -125,9 +117,7 @@ const customDynamicTextColor = DynamicColorIOS({
</Text>;
```

<p className="snippet-caption">
 Changes the text color based on the system theme
</p>
<p className="snippet-caption">Changes the text color based on the system theme</p>

You can learn more about `DynamicColorIOS` from [the documentation](https://reactnative.dev/docs/dynamiccolorios).

Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.70/appregistry.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: AppRegistry

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.
 </p>
 <p>If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.</p>
</div>

`AppRegistry` is the JS entry point to running all React Native apps. App root components should register themselves with `AppRegistry.registerComponent`, then the native system can load the bundle for the app and then actually run the app when it's ready by invoking `AppRegistry.runApplication`.
Expand Down

6 changes: 2 additions & 4 deletions
website/versioned_docs/version-0.70/debugging.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -164,10 +164,8 @@ You can view installation instructions [in the README](https://github.com/infini
# Native Debugging

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.
 </p>
 <h3>Projects with Native Code Only</h3><p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.</p>
</div>

## Accessing console logs
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.70/linking.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -30,9 +30,7 @@ As mentioned in the introduction, there are some URL schemes for core functional

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.</p>
</div>

If you want to enable deep links in your app, please read the below guide:
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.70/permissionsandroid.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import con

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.</p>
</div>

`PermissionsAndroid` provides access to Android M's new permissions model. The so-called "normal" permissions are granted by default when the application is installed as long as they appear in `AndroidManifest.xml`. However, "dangerous" permissions require a dialog prompt. You should use this module for those permissions.
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.70/pushnotificationios.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ title: '🚧 PushNotificationIOS'

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.</p>
</div>

Handle push notifications for your app, including permission handling and icon badge number.
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.71/appregistry.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: AppRegistry

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.
 </p>
 <p>If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.</p>
</div>

`AppRegistry` is the JS entry point to running all React Native apps. App root components should register themselves with `AppRegistry.registerComponent`, then the native system can load the bundle for the app and then actually run the app when it's ready by invoking `AppRegistry.runApplication`.
Expand Down

6 changes: 2 additions & 4 deletions
website/versioned_docs/version-0.71/debugging.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -164,10 +164,8 @@ You can view installation instructions [in the README](https://github.com/infini
# Native Debugging

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.
 </p>
 <h3>Projects with Native Code Only</h3><p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.</p>
</div>

## Accessing console logs
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.71/linking.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -30,9 +30,7 @@ As mentioned in the introduction, there are some URL schemes for core functional

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.</p>
</div>

If you want to enable deep links in your app, please read the below guide:
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.71/permissionsandroid.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import con

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.</p>
</div>

`PermissionsAndroid` provides access to Android M's new permissions model. The so-called "normal" permissions are granted by default when the application is installed as long as they appear in `AndroidManifest.xml`. However, "dangerous" permissions require a dialog prompt. You should use this module for those permissions.
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.71/pushnotificationios.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ title: '🚧 PushNotificationIOS'

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.</p>
</div>

Handle push notifications for your app, including permission handling and icon badge number.
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.72/appregistry.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: AppRegistry

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.
 </p>
 <p>If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.</p>
</div>

`AppRegistry` is the JS entry point to running all React Native apps. App root components should register themselves with `AppRegistry.registerComponent`, then the native system can load the bundle for the app and then actually run the app when it's ready by invoking `AppRegistry.runApplication`.
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.72/linking.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -30,9 +30,7 @@ As mentioned in the introduction, there are some URL schemes for core functional

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.</p>
</div>

If you want to enable deep links in your app, please read the below guide:
Expand Down

6 changes: 2 additions & 4 deletions
website/versioned_docs/version-0.72/native-debugging.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -6,10 +6,8 @@ title: Native Debugging
import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import constants from '@site/core/TabsConstants';

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.
 </p>
 <h3>Projects with Native Code Only</h3><p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.</p>
</div>

## Accessing native logs
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.72/permissionsandroid.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: PermissionsAndroid

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.</p>
</div>

`PermissionsAndroid` provides access to Android M's new permissions model. The so-called "normal" permissions are granted by default when the application is installed as long as they appear in `AndroidManifest.xml`. However, "dangerous" permissions require a dialog prompt. You should use this module for those permissions.
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.72/pushnotificationios.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ title: '🚧 PushNotificationIOS'

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.</p>
</div>

Handle push notifications for your app, including permission handling and icon badge number.
Expand Down
Loading

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Highlight search terms from Google/DuckDuckGo/Bing referrer
(function() {
var ref = document.referrer;
var terms = [];
if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {
var url = new URL(ref);
var q = url.searchParams.get('q') || url.searchParams.get('p');
if (q) {
terms = q.split(/\s+/).filter(function(t) { return t.length > 2; });
}
}
if (terms.length === 0) return;
var style = document.createElement('style');
style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';
document.head.appendChild(style);
function highlight(node) {
if (node.nodeType === 3) { // text node
var text = node.textContent;
var found = false;
terms.forEach(function(term) {
var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi');
if (regex.test(text)) {
found = true;
var frag = document.createDocumentFragment();
var parts = text.split(regex);
parts.forEach(function(part, i) {
if (i % 2 === 0) {
frag.appendChild(document.createTextNode(part));
} else {
var span = document.createElement('span');
span.className = 'userscript-highlight';
span.textContent = part;
frag.appendChild(span);
}
});
node.parentNode.replaceChild(frag, node);
}
});
} else if (node.nodeType === 1 && node.childNodes) { // element
var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];
if (!skipTags.includes(node.tagName)) {
Array.from(node.childNodes).forEach(highlight);
}
}
}
highlight(document.body);
// Re-highlight on dynamic content
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1 || node.nodeType === 3) highlight(node);
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
Fix MDX double `<p>` tags by slorber · Pull Request #4267 · react/react-native-website · GitHub
Skip to content
Fix MDX double <p> tags#4267

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

 Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

 Merged

Simek
merged 1 commit into

from

Oct 10, 2024
 Merged


Fix MDX double <p> tags
#4267
Show file tree
Hide file tree
 Changes from all commits
Commits

Show all changes


1 commit


Select commit


File filter

Filter by extension
Filter by extension
Conversations

Failed to load comments. 
Loading
Jump to

Jump to file


Failed to load files. 
Loading
 Diff view

 Diff view


4 changes: 1 addition & 3 deletions
docs/appregistry.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: AppRegistry

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.
 </p>
 <p>If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.</p>
</div>

`AppRegistry` is the JS entry point to running all React Native apps. App root components should register themselves with `AppRegistry.registerComponent`, then the native system can load the bundle for the app and then actually run the app when it's ready by invoking `AppRegistry.runApplication`.
Expand Down

4 changes: 1 addition & 3 deletions
docs/debugging-native-code.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import con

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.</p>
</div>

## Accessing Logs
Expand Down

4 changes: 1 addition & 3 deletions
docs/linking.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -30,9 +30,7 @@ As mentioned in the introduction, there are some URL schemes for core functional

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.</p>
</div>

If you want to enable deep links in your app, please read the below guide:
Expand Down

4 changes: 1 addition & 3 deletions
docs/permissionsandroid.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: PermissionsAndroid

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.</p>
</div>

`PermissionsAndroid` provides access to Android M's new permissions model. The so-called "normal" permissions are granted by default when the application is installed as long as they appear in `AndroidManifest.xml`. However, "dangerous" permissions require a dialog prompt. You should use this module for those permissions.
Expand Down

4 changes: 1 addition & 3 deletions
docs/pushnotificationios.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ title: '🚧 PushNotificationIOS'

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.</p>
</div>

Handle notifications for your app, including scheduling and permissions.
Expand Down

18 changes: 4 additions & 14 deletions
website/blog/2020-07-06-version-0.63.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -61,9 +61,7 @@ import {Pressable, Text} from 'react-native';
</Pressable>;
```

<p className="snippet-caption">
 A simple example of a Pressable component in action
</p>
<p className="snippet-caption">A simple example of a Pressable component in action</p>

You can learn more about it from [the documentation](https://reactnative.dev/docs/pressable).

Expand All@@ -85,10 +83,7 @@ import {Text, PlatformColor} from 'react-native';
</Text>;
```

<p className="snippet-caption">
 Sets the color of the Text component to labelColor as defined by
 iOS.
</p>
<p className="snippet-caption">Sets the color of the Text component to labelColor as defined by iOS.</p>

Android, on the other hand, [provides colors like colorButtonNormal](https://developer.android.com/reference/android/R.attr#colorButtonNormal). You can use this color in React Native with:

Expand All@@ -103,10 +98,7 @@ import {View, Text, PlatformColor} from 'react-native';
</View>;
```

<p className="snippet-caption">
 Sets the background color of the View component to
 colorButtonNormal as defined by Android.
</p>
<p className="snippet-caption">Sets the background color of the View component to colorButtonNormal as defined by Android.</p>

You can learn more about `PlatformColor` from [the documentation](https://reactnative.dev/docs/platformcolor). You can also check the actual [code examples present in the RNTester](https://github.com/facebook/react-native/blob/master/packages/rn-tester/js/examples/PlatformColor/PlatformColorExample.js).

Expand All@@ -125,9 +117,7 @@ const customDynamicTextColor = DynamicColorIOS({
</Text>;
```

<p className="snippet-caption">
 Changes the text color based on the system theme
</p>
<p className="snippet-caption">Changes the text color based on the system theme</p>

You can learn more about `DynamicColorIOS` from [the documentation](https://reactnative.dev/docs/dynamiccolorios).

Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.70/appregistry.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: AppRegistry

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.
 </p>
 <p>If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.</p>
</div>

`AppRegistry` is the JS entry point to running all React Native apps. App root components should register themselves with `AppRegistry.registerComponent`, then the native system can load the bundle for the app and then actually run the app when it's ready by invoking `AppRegistry.runApplication`.
Expand Down

6 changes: 2 additions & 4 deletions
website/versioned_docs/version-0.70/debugging.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -164,10 +164,8 @@ You can view installation instructions [in the README](https://github.com/infini
# Native Debugging

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.
 </p>
 <h3>Projects with Native Code Only</h3><p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.</p>
</div>

## Accessing console logs
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.70/linking.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -30,9 +30,7 @@ As mentioned in the introduction, there are some URL schemes for core functional

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.</p>
</div>

If you want to enable deep links in your app, please read the below guide:
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.70/permissionsandroid.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import con

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.</p>
</div>

`PermissionsAndroid` provides access to Android M's new permissions model. The so-called "normal" permissions are granted by default when the application is installed as long as they appear in `AndroidManifest.xml`. However, "dangerous" permissions require a dialog prompt. You should use this module for those permissions.
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.70/pushnotificationios.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ title: '🚧 PushNotificationIOS'

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.</p>
</div>

Handle push notifications for your app, including permission handling and icon badge number.
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.71/appregistry.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: AppRegistry

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.
 </p>
 <p>If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.</p>
</div>

`AppRegistry` is the JS entry point to running all React Native apps. App root components should register themselves with `AppRegistry.registerComponent`, then the native system can load the bundle for the app and then actually run the app when it's ready by invoking `AppRegistry.runApplication`.
Expand Down

6 changes: 2 additions & 4 deletions
website/versioned_docs/version-0.71/debugging.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -164,10 +164,8 @@ You can view installation instructions [in the README](https://github.com/infini
# Native Debugging

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.
 </p>
 <h3>Projects with Native Code Only</h3><p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.</p>
</div>

## Accessing console logs
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.71/linking.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -30,9 +30,7 @@ As mentioned in the introduction, there are some URL schemes for core functional

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.</p>
</div>

If you want to enable deep links in your app, please read the below guide:
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.71/permissionsandroid.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import con

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.</p>
</div>

`PermissionsAndroid` provides access to Android M's new permissions model. The so-called "normal" permissions are granted by default when the application is installed as long as they appear in `AndroidManifest.xml`. However, "dangerous" permissions require a dialog prompt. You should use this module for those permissions.
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.71/pushnotificationios.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ title: '🚧 PushNotificationIOS'

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.</p>
</div>

Handle push notifications for your app, including permission handling and icon badge number.
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.72/appregistry.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: AppRegistry

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.
 </p>
 <p>If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.</p>
</div>

`AppRegistry` is the JS entry point to running all React Native apps. App root components should register themselves with `AppRegistry.registerComponent`, then the native system can load the bundle for the app and then actually run the app when it's ready by invoking `AppRegistry.runApplication`.
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.72/linking.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -30,9 +30,7 @@ As mentioned in the introduction, there are some URL schemes for core functional

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.</p>
</div>

If you want to enable deep links in your app, please read the below guide:
Expand Down

6 changes: 2 additions & 4 deletions
website/versioned_docs/version-0.72/native-debugging.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -6,10 +6,8 @@ title: Native Debugging
import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import constants from '@site/core/TabsConstants';

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.
 </p>
 <h3>Projects with Native Code Only</h3><p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.</p>
</div>

## Accessing native logs
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.72/permissionsandroid.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: PermissionsAndroid

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.</p>
</div>

`PermissionsAndroid` provides access to Android M's new permissions model. The so-called "normal" permissions are granted by default when the application is installed as long as they appear in `AndroidManifest.xml`. However, "dangerous" permissions require a dialog prompt. You should use this module for those permissions.
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.72/pushnotificationios.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ title: '🚧 PushNotificationIOS'

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.</p>
</div>

Handle push notifications for your app, including permission handling and icon badge number.
Expand Down
Loading

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Strip utm_, fbclid, gclid, etc. from all links on page
(function() {
var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',
'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',
'ref', 'ref_src', 'source', 'medium', 'campaign'];
function cleanUrl(url) {
try {
var u = new URL(url, window.location.origin);
var changed = false;
trackingParams.forEach(function(p) {
if (u.searchParams.has(p)) {
u.searchParams.delete(p);
changed = true;
}
});
return changed ? u.toString() : url;
} catch (e) {
return url;
}
}
function cleanLinks() {
document.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
cleanLinks();
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1) {
if (node.tagName === 'A') cleanLinks();
node.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '
Fix MDX double `<p>` tags by slorber · Pull Request #4267 · react/react-native-website · GitHub
Skip to content
Fix MDX double <p> tags#4267

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

 Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

 Merged

Simek
merged 1 commit into

from

Oct 10, 2024
 Merged


Fix MDX double <p> tags
#4267
Show file tree
Hide file tree
 Changes from all commits
Commits

Show all changes


1 commit


Select commit


File filter

Filter by extension
Filter by extension
Conversations

Failed to load comments. 
Loading
Jump to

Jump to file


Failed to load files. 
Loading
 Diff view

 Diff view


4 changes: 1 addition & 3 deletions
docs/appregistry.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: AppRegistry

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.
 </p>
 <p>If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.</p>
</div>

`AppRegistry` is the JS entry point to running all React Native apps. App root components should register themselves with `AppRegistry.registerComponent`, then the native system can load the bundle for the app and then actually run the app when it's ready by invoking `AppRegistry.runApplication`.
Expand Down

4 changes: 1 addition & 3 deletions
docs/debugging-native-code.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import con

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.</p>
</div>

## Accessing Logs
Expand Down

4 changes: 1 addition & 3 deletions
docs/linking.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -30,9 +30,7 @@ As mentioned in the introduction, there are some URL schemes for core functional

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.</p>
</div>

If you want to enable deep links in your app, please read the below guide:
Expand Down

4 changes: 1 addition & 3 deletions
docs/permissionsandroid.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: PermissionsAndroid

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.</p>
</div>

`PermissionsAndroid` provides access to Android M's new permissions model. The so-called "normal" permissions are granted by default when the application is installed as long as they appear in `AndroidManifest.xml`. However, "dangerous" permissions require a dialog prompt. You should use this module for those permissions.
Expand Down

4 changes: 1 addition & 3 deletions
docs/pushnotificationios.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ title: '🚧 PushNotificationIOS'

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.</p>
</div>

Handle notifications for your app, including scheduling and permissions.
Expand Down

18 changes: 4 additions & 14 deletions
website/blog/2020-07-06-version-0.63.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -61,9 +61,7 @@ import {Pressable, Text} from 'react-native';
</Pressable>;
```

<p className="snippet-caption">
 A simple example of a Pressable component in action
</p>
<p className="snippet-caption">A simple example of a Pressable component in action</p>

You can learn more about it from [the documentation](https://reactnative.dev/docs/pressable).

Expand All@@ -85,10 +83,7 @@ import {Text, PlatformColor} from 'react-native';
</Text>;
```

<p className="snippet-caption">
 Sets the color of the Text component to labelColor as defined by
 iOS.
</p>
<p className="snippet-caption">Sets the color of the Text component to labelColor as defined by iOS.</p>

Android, on the other hand, [provides colors like colorButtonNormal](https://developer.android.com/reference/android/R.attr#colorButtonNormal). You can use this color in React Native with:

Expand All@@ -103,10 +98,7 @@ import {View, Text, PlatformColor} from 'react-native';
</View>;
```

<p className="snippet-caption">
 Sets the background color of the View component to
 colorButtonNormal as defined by Android.
</p>
<p className="snippet-caption">Sets the background color of the View component to colorButtonNormal as defined by Android.</p>

You can learn more about `PlatformColor` from [the documentation](https://reactnative.dev/docs/platformcolor). You can also check the actual [code examples present in the RNTester](https://github.com/facebook/react-native/blob/master/packages/rn-tester/js/examples/PlatformColor/PlatformColorExample.js).

Expand All@@ -125,9 +117,7 @@ const customDynamicTextColor = DynamicColorIOS({
</Text>;
```

<p className="snippet-caption">
 Changes the text color based on the system theme
</p>
<p className="snippet-caption">Changes the text color based on the system theme</p>

You can learn more about `DynamicColorIOS` from [the documentation](https://reactnative.dev/docs/dynamiccolorios).

Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.70/appregistry.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: AppRegistry

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.
 </p>
 <p>If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.</p>
</div>

`AppRegistry` is the JS entry point to running all React Native apps. App root components should register themselves with `AppRegistry.registerComponent`, then the native system can load the bundle for the app and then actually run the app when it's ready by invoking `AppRegistry.runApplication`.
Expand Down

6 changes: 2 additions & 4 deletions
website/versioned_docs/version-0.70/debugging.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -164,10 +164,8 @@ You can view installation instructions [in the README](https://github.com/infini
# Native Debugging

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.
 </p>
 <h3>Projects with Native Code Only</h3><p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.</p>
</div>

## Accessing console logs
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.70/linking.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -30,9 +30,7 @@ As mentioned in the introduction, there are some URL schemes for core functional

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.</p>
</div>

If you want to enable deep links in your app, please read the below guide:
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.70/permissionsandroid.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import con

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.</p>
</div>

`PermissionsAndroid` provides access to Android M's new permissions model. The so-called "normal" permissions are granted by default when the application is installed as long as they appear in `AndroidManifest.xml`. However, "dangerous" permissions require a dialog prompt. You should use this module for those permissions.
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.70/pushnotificationios.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ title: '🚧 PushNotificationIOS'

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.</p>
</div>

Handle push notifications for your app, including permission handling and icon badge number.
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.71/appregistry.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: AppRegistry

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.
 </p>
 <p>If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.</p>
</div>

`AppRegistry` is the JS entry point to running all React Native apps. App root components should register themselves with `AppRegistry.registerComponent`, then the native system can load the bundle for the app and then actually run the app when it's ready by invoking `AppRegistry.runApplication`.
Expand Down

6 changes: 2 additions & 4 deletions
website/versioned_docs/version-0.71/debugging.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -164,10 +164,8 @@ You can view installation instructions [in the README](https://github.com/infini
# Native Debugging

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.
 </p>
 <h3>Projects with Native Code Only</h3><p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.</p>
</div>

## Accessing console logs
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.71/linking.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -30,9 +30,7 @@ As mentioned in the introduction, there are some URL schemes for core functional

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.</p>
</div>

If you want to enable deep links in your app, please read the below guide:
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.71/permissionsandroid.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import con

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.</p>
</div>

`PermissionsAndroid` provides access to Android M's new permissions model. The so-called "normal" permissions are granted by default when the application is installed as long as they appear in `AndroidManifest.xml`. However, "dangerous" permissions require a dialog prompt. You should use this module for those permissions.
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.71/pushnotificationios.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ title: '🚧 PushNotificationIOS'

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.</p>
</div>

Handle push notifications for your app, including permission handling and icon badge number.
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.72/appregistry.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: AppRegistry

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.
 </p>
 <p>If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.</p>
</div>

`AppRegistry` is the JS entry point to running all React Native apps. App root components should register themselves with `AppRegistry.registerComponent`, then the native system can load the bundle for the app and then actually run the app when it's ready by invoking `AppRegistry.runApplication`.
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.72/linking.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -30,9 +30,7 @@ As mentioned in the introduction, there are some URL schemes for core functional

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.</p>
</div>

If you want to enable deep links in your app, please read the below guide:
Expand Down

6 changes: 2 additions & 4 deletions
website/versioned_docs/version-0.72/native-debugging.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -6,10 +6,8 @@ title: Native Debugging
import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import constants from '@site/core/TabsConstants';

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.
 </p>
 <h3>Projects with Native Code Only</h3><p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.</p>
</div>

## Accessing native logs
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.72/permissionsandroid.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: PermissionsAndroid

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.</p>
</div>

`PermissionsAndroid` provides access to Android M's new permissions model. The so-called "normal" permissions are granted by default when the application is installed as long as they appear in `AndroidManifest.xml`. However, "dangerous" permissions require a dialog prompt. You should use this module for those permissions.
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.72/pushnotificationios.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ title: '🚧 PushNotificationIOS'

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.</p>
</div>

Handle push notifications for your app, including permission handling and icon badge number.
Expand Down
Loading

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Auto-enable theater mode on YouTube
(function() {
function tryTheater() {
var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]');
if (btn && !btn.classList.contains('activated')) {
btn.click();
}
}
// Try immediately
tryTheater();
// Try after navigation (SPA)
var lastUrl = location.href;
setInterval(function() {
if (location.href !== lastUrl) {
lastUrl = location.href;
setTimeout(tryTheater, 500);
}
}, 1000);
// Also try on player load
var observer = new MutationObserver(tryTheater);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
Fix MDX double `<p>` tags by slorber · Pull Request #4267 · react/react-native-website · GitHub
Skip to content
Fix MDX double <p> tags#4267

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

 Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

 Merged

Simek
merged 1 commit into

from

Oct 10, 2024
 Merged


Fix MDX double <p> tags
#4267
Show file tree
Hide file tree
 Changes from all commits
Commits

Show all changes


1 commit


Select commit


File filter

Filter by extension
Filter by extension
Conversations

Failed to load comments. 
Loading
Jump to

Jump to file


Failed to load files. 
Loading
 Diff view

 Diff view


4 changes: 1 addition & 3 deletions
docs/appregistry.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: AppRegistry

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.
 </p>
 <p>If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.</p>
</div>

`AppRegistry` is the JS entry point to running all React Native apps. App root components should register themselves with `AppRegistry.registerComponent`, then the native system can load the bundle for the app and then actually run the app when it's ready by invoking `AppRegistry.runApplication`.
Expand Down

4 changes: 1 addition & 3 deletions
docs/debugging-native-code.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import con

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.</p>
</div>

## Accessing Logs
Expand Down

4 changes: 1 addition & 3 deletions
docs/linking.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -30,9 +30,7 @@ As mentioned in the introduction, there are some URL schemes for core functional

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.</p>
</div>

If you want to enable deep links in your app, please read the below guide:
Expand Down

4 changes: 1 addition & 3 deletions
docs/permissionsandroid.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: PermissionsAndroid

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.</p>
</div>

`PermissionsAndroid` provides access to Android M's new permissions model. The so-called "normal" permissions are granted by default when the application is installed as long as they appear in `AndroidManifest.xml`. However, "dangerous" permissions require a dialog prompt. You should use this module for those permissions.
Expand Down

4 changes: 1 addition & 3 deletions
docs/pushnotificationios.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ title: '🚧 PushNotificationIOS'

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.</p>
</div>

Handle notifications for your app, including scheduling and permissions.
Expand Down

18 changes: 4 additions & 14 deletions
website/blog/2020-07-06-version-0.63.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -61,9 +61,7 @@ import {Pressable, Text} from 'react-native';
</Pressable>;
```

<p className="snippet-caption">
 A simple example of a Pressable component in action
</p>
<p className="snippet-caption">A simple example of a Pressable component in action</p>

You can learn more about it from [the documentation](https://reactnative.dev/docs/pressable).

Expand All@@ -85,10 +83,7 @@ import {Text, PlatformColor} from 'react-native';
</Text>;
```

<p className="snippet-caption">
 Sets the color of the Text component to labelColor as defined by
 iOS.
</p>
<p className="snippet-caption">Sets the color of the Text component to labelColor as defined by iOS.</p>

Android, on the other hand, [provides colors like colorButtonNormal](https://developer.android.com/reference/android/R.attr#colorButtonNormal). You can use this color in React Native with:

Expand All@@ -103,10 +98,7 @@ import {View, Text, PlatformColor} from 'react-native';
</View>;
```

<p className="snippet-caption">
 Sets the background color of the View component to
 colorButtonNormal as defined by Android.
</p>
<p className="snippet-caption">Sets the background color of the View component to colorButtonNormal as defined by Android.</p>

You can learn more about `PlatformColor` from [the documentation](https://reactnative.dev/docs/platformcolor). You can also check the actual [code examples present in the RNTester](https://github.com/facebook/react-native/blob/master/packages/rn-tester/js/examples/PlatformColor/PlatformColorExample.js).

Expand All@@ -125,9 +117,7 @@ const customDynamicTextColor = DynamicColorIOS({
</Text>;
```

<p className="snippet-caption">
 Changes the text color based on the system theme
</p>
<p className="snippet-caption">Changes the text color based on the system theme</p>

You can learn more about `DynamicColorIOS` from [the documentation](https://reactnative.dev/docs/dynamiccolorios).

Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.70/appregistry.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: AppRegistry

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.
 </p>
 <p>If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.</p>
</div>

`AppRegistry` is the JS entry point to running all React Native apps. App root components should register themselves with `AppRegistry.registerComponent`, then the native system can load the bundle for the app and then actually run the app when it's ready by invoking `AppRegistry.runApplication`.
Expand Down

6 changes: 2 additions & 4 deletions
website/versioned_docs/version-0.70/debugging.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -164,10 +164,8 @@ You can view installation instructions [in the README](https://github.com/infini
# Native Debugging

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.
 </p>
 <h3>Projects with Native Code Only</h3><p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.</p>
</div>

## Accessing console logs
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.70/linking.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -30,9 +30,7 @@ As mentioned in the introduction, there are some URL schemes for core functional

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.</p>
</div>

If you want to enable deep links in your app, please read the below guide:
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.70/permissionsandroid.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import con

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.</p>
</div>

`PermissionsAndroid` provides access to Android M's new permissions model. The so-called "normal" permissions are granted by default when the application is installed as long as they appear in `AndroidManifest.xml`. However, "dangerous" permissions require a dialog prompt. You should use this module for those permissions.
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.70/pushnotificationios.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ title: '🚧 PushNotificationIOS'

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.</p>
</div>

Handle push notifications for your app, including permission handling and icon badge number.
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.71/appregistry.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: AppRegistry

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.
 </p>
 <p>If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.</p>
</div>

`AppRegistry` is the JS entry point to running all React Native apps. App root components should register themselves with `AppRegistry.registerComponent`, then the native system can load the bundle for the app and then actually run the app when it's ready by invoking `AppRegistry.runApplication`.
Expand Down

6 changes: 2 additions & 4 deletions
website/versioned_docs/version-0.71/debugging.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -164,10 +164,8 @@ You can view installation instructions [in the README](https://github.com/infini
# Native Debugging

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.
 </p>
 <h3>Projects with Native Code Only</h3><p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.</p>
</div>

## Accessing console logs
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.71/linking.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -30,9 +30,7 @@ As mentioned in the introduction, there are some URL schemes for core functional

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.</p>
</div>

If you want to enable deep links in your app, please read the below guide:
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.71/permissionsandroid.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import con

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.</p>
</div>

`PermissionsAndroid` provides access to Android M's new permissions model. The so-called "normal" permissions are granted by default when the application is installed as long as they appear in `AndroidManifest.xml`. However, "dangerous" permissions require a dialog prompt. You should use this module for those permissions.
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.71/pushnotificationios.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ title: '🚧 PushNotificationIOS'

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.</p>
</div>

Handle push notifications for your app, including permission handling and icon badge number.
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.72/appregistry.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: AppRegistry

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.
 </p>
 <p>If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.</p>
</div>

`AppRegistry` is the JS entry point to running all React Native apps. App root components should register themselves with `AppRegistry.registerComponent`, then the native system can load the bundle for the app and then actually run the app when it's ready by invoking `AppRegistry.runApplication`.
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.72/linking.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -30,9 +30,7 @@ As mentioned in the introduction, there are some URL schemes for core functional

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.</p>
</div>

If you want to enable deep links in your app, please read the below guide:
Expand Down

6 changes: 2 additions & 4 deletions
website/versioned_docs/version-0.72/native-debugging.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -6,10 +6,8 @@ title: Native Debugging
import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import constants from '@site/core/TabsConstants';

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.
 </p>
 <h3>Projects with Native Code Only</h3><p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.</p>
</div>

## Accessing native logs
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.72/permissionsandroid.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: PermissionsAndroid

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.</p>
</div>

`PermissionsAndroid` provides access to Android M's new permissions model. The so-called "normal" permissions are granted by default when the application is installed as long as they appear in `AndroidManifest.xml`. However, "dangerous" permissions require a dialog prompt. You should use this module for those permissions.
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.72/pushnotificationios.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ title: '🚧 PushNotificationIOS'

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.</p>
</div>

Handle push notifications for your app, including permission handling and icon badge number.
Expand Down
Loading

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Remove or un-stick sticky/fixed headers that block content
(function() {
function unstick() {
document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) {
if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {
el.style.position = 'static';
el.style.top = 'auto';
el.style.zIndex = 'auto';
}
});
}
unstick();
var observer = new MutationObserver(unstick);
observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });
})();
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
Fix MDX double `<p>` tags by slorber · Pull Request #4267 · react/react-native-website · GitHub
Skip to content
Fix MDX double <p> tags#4267

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

 Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

 Merged

Simek
merged 1 commit into

from

Oct 10, 2024
 Merged


Fix MDX double <p> tags
#4267
Show file tree
Hide file tree
 Changes from all commits
Commits

Show all changes


1 commit


Select commit


File filter

Filter by extension
Filter by extension
Conversations

Failed to load comments. 
Loading
Jump to

Jump to file


Failed to load files. 
Loading
 Diff view

 Diff view


4 changes: 1 addition & 3 deletions
docs/appregistry.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: AppRegistry

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.
 </p>
 <p>If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.</p>
</div>

`AppRegistry` is the JS entry point to running all React Native apps. App root components should register themselves with `AppRegistry.registerComponent`, then the native system can load the bundle for the app and then actually run the app when it's ready by invoking `AppRegistry.runApplication`.
Expand Down

4 changes: 1 addition & 3 deletions
docs/debugging-native-code.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import con

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.</p>
</div>

## Accessing Logs
Expand Down

4 changes: 1 addition & 3 deletions
docs/linking.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -30,9 +30,7 @@ As mentioned in the introduction, there are some URL schemes for core functional

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.</p>
</div>

If you want to enable deep links in your app, please read the below guide:
Expand Down

4 changes: 1 addition & 3 deletions
docs/permissionsandroid.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: PermissionsAndroid

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.</p>
</div>

`PermissionsAndroid` provides access to Android M's new permissions model. The so-called "normal" permissions are granted by default when the application is installed as long as they appear in `AndroidManifest.xml`. However, "dangerous" permissions require a dialog prompt. You should use this module for those permissions.
Expand Down

4 changes: 1 addition & 3 deletions
docs/pushnotificationios.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ title: '🚧 PushNotificationIOS'

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.</p>
</div>

Handle notifications for your app, including scheduling and permissions.
Expand Down

18 changes: 4 additions & 14 deletions
website/blog/2020-07-06-version-0.63.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -61,9 +61,7 @@ import {Pressable, Text} from 'react-native';
</Pressable>;
```

<p className="snippet-caption">
 A simple example of a Pressable component in action
</p>
<p className="snippet-caption">A simple example of a Pressable component in action</p>

You can learn more about it from [the documentation](https://reactnative.dev/docs/pressable).

Expand All@@ -85,10 +83,7 @@ import {Text, PlatformColor} from 'react-native';
</Text>;
```

<p className="snippet-caption">
 Sets the color of the Text component to labelColor as defined by
 iOS.
</p>
<p className="snippet-caption">Sets the color of the Text component to labelColor as defined by iOS.</p>

Android, on the other hand, [provides colors like colorButtonNormal](https://developer.android.com/reference/android/R.attr#colorButtonNormal). You can use this color in React Native with:

Expand All@@ -103,10 +98,7 @@ import {View, Text, PlatformColor} from 'react-native';
</View>;
```

<p className="snippet-caption">
 Sets the background color of the View component to
 colorButtonNormal as defined by Android.
</p>
<p className="snippet-caption">Sets the background color of the View component to colorButtonNormal as defined by Android.</p>

You can learn more about `PlatformColor` from [the documentation](https://reactnative.dev/docs/platformcolor). You can also check the actual [code examples present in the RNTester](https://github.com/facebook/react-native/blob/master/packages/rn-tester/js/examples/PlatformColor/PlatformColorExample.js).

Expand All@@ -125,9 +117,7 @@ const customDynamicTextColor = DynamicColorIOS({
</Text>;
```

<p className="snippet-caption">
 Changes the text color based on the system theme
</p>
<p className="snippet-caption">Changes the text color based on the system theme</p>

You can learn more about `DynamicColorIOS` from [the documentation](https://reactnative.dev/docs/dynamiccolorios).

Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.70/appregistry.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: AppRegistry

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.
 </p>
 <p>If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.</p>
</div>

`AppRegistry` is the JS entry point to running all React Native apps. App root components should register themselves with `AppRegistry.registerComponent`, then the native system can load the bundle for the app and then actually run the app when it's ready by invoking `AppRegistry.runApplication`.
Expand Down

6 changes: 2 additions & 4 deletions
website/versioned_docs/version-0.70/debugging.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -164,10 +164,8 @@ You can view installation instructions [in the README](https://github.com/infini
# Native Debugging

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.
 </p>
 <h3>Projects with Native Code Only</h3><p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.</p>
</div>

## Accessing console logs
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.70/linking.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -30,9 +30,7 @@ As mentioned in the introduction, there are some URL schemes for core functional

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.</p>
</div>

If you want to enable deep links in your app, please read the below guide:
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.70/permissionsandroid.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import con

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.</p>
</div>

`PermissionsAndroid` provides access to Android M's new permissions model. The so-called "normal" permissions are granted by default when the application is installed as long as they appear in `AndroidManifest.xml`. However, "dangerous" permissions require a dialog prompt. You should use this module for those permissions.
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.70/pushnotificationios.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ title: '🚧 PushNotificationIOS'

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.</p>
</div>

Handle push notifications for your app, including permission handling and icon badge number.
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.71/appregistry.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: AppRegistry

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.
 </p>
 <p>If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.</p>
</div>

`AppRegistry` is the JS entry point to running all React Native apps. App root components should register themselves with `AppRegistry.registerComponent`, then the native system can load the bundle for the app and then actually run the app when it's ready by invoking `AppRegistry.runApplication`.
Expand Down

6 changes: 2 additions & 4 deletions
website/versioned_docs/version-0.71/debugging.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -164,10 +164,8 @@ You can view installation instructions [in the README](https://github.com/infini
# Native Debugging

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.
 </p>
 <h3>Projects with Native Code Only</h3><p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.</p>
</div>

## Accessing console logs
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.71/linking.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -30,9 +30,7 @@ As mentioned in the introduction, there are some URL schemes for core functional

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.</p>
</div>

If you want to enable deep links in your app, please read the below guide:
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.71/permissionsandroid.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import con

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.</p>
</div>

`PermissionsAndroid` provides access to Android M's new permissions model. The so-called "normal" permissions are granted by default when the application is installed as long as they appear in `AndroidManifest.xml`. However, "dangerous" permissions require a dialog prompt. You should use this module for those permissions.
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.71/pushnotificationios.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ title: '🚧 PushNotificationIOS'

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.</p>
</div>

Handle push notifications for your app, including permission handling and icon badge number.
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.72/appregistry.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: AppRegistry

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.
 </p>
 <p>If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.</p>
</div>

`AppRegistry` is the JS entry point to running all React Native apps. App root components should register themselves with `AppRegistry.registerComponent`, then the native system can load the bundle for the app and then actually run the app when it's ready by invoking `AppRegistry.runApplication`.
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.72/linking.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -30,9 +30,7 @@ As mentioned in the introduction, there are some URL schemes for core functional

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.</p>
</div>

If you want to enable deep links in your app, please read the below guide:
Expand Down

6 changes: 2 additions & 4 deletions
website/versioned_docs/version-0.72/native-debugging.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -6,10 +6,8 @@ title: Native Debugging
import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import constants from '@site/core/TabsConstants';

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.
 </p>
 <h3>Projects with Native Code Only</h3><p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.</p>
</div>

## Accessing native logs
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.72/permissionsandroid.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: PermissionsAndroid

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.</p>
</div>

`PermissionsAndroid` provides access to Android M's new permissions model. The so-called "normal" permissions are granted by default when the application is installed as long as they appear in `AndroidManifest.xml`. However, "dangerous" permissions require a dialog prompt. You should use this module for those permissions.
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.72/pushnotificationios.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ title: '🚧 PushNotificationIOS'

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.</p>
</div>

Handle push notifications for your app, including permission handling and icon badge number.
Expand Down
Loading

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Universal Dark Mode - works on any site
(function() {
var enabled = true;
function applyDarkMode() {
if (!enabled) return;
// Create style element if it doesn't exist
var style = document.getElementById('universal-dark-mode-style');
if (!style) {
style = document.createElement('style');
style.id = 'universal-dark-mode-style';
document.head.appendChild(style);
}
// Dark mode CSS - inverts colors but preserves images/video
style.textContent = '
/* Invert everything except media */
html {
filter: invert(1) hue-rotate(180deg) !important;
background: #1a1a2e !important;
}
/* Restore images, videos, iframes, canvas */
img, video, iframe, canvas, svg, picture, [style*="background-image"] {
filter: invert(1) hue-rotate(180deg) !important;
}
/* Preserve specific elements that should not be inverted */
.no-dark-mode, .no-dark-mode *,
[data-theme="light"], [data-theme="light"],
.ace_editor, .ace_editor *,
.CodeMirror, .CodeMirror *,
.monaco-editor, .monaco-editor *,
.markdown-body pre, .markdown-body pre *,
.highlight, .highlight *,
pre code, pre code * {
filter: none !important;
}
/* Fix common UI elements */
.modal, .popup, .dropdown-menu, .tooltip, .popover {
filter: invert(1) hue-rotate(180deg) !important;
background: #2d2d44 !important;
border-color: #444 !important;
}
/* Scrollbars */
::-webkit-scrollbar { background: #1a1a2e !important; }
::-webkit-scrollbar-thumb { background: #444 !important; }
::-webkit-scrollbar-thumb:hover { background: #555 !important; }
/* Selection */
::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
';
}
function removeDarkMode() {
var style = document.getElementById('universal-dark-mode-style');
if (style) style.remove();
}
// Toggle with Alt+Shift+D
document.addEventListener('keydown', function(e) {
if (e.altKey && e.shiftKey && e.key === 'D') {
e.preventDefault();
enabled = !enabled;
if (enabled) {
applyDarkMode();
console.log('[Universal Dark Mode] Enabled');
} else {
removeDarkMode();
console.log('[Universal Dark Mode] Disabled');
}
}
});
// Apply on load
applyDarkMode();
// Re-apply on dynamic content
var observer = new MutationObserver(function(mutations) {
if (enabled && !document.getElementById('universal-dark-mode-style')) {
applyDarkMode();
}
});
observer.observe(document.head, { childList: true });
console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');
})();
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();
Fix MDX double `<p>` tags by slorber · Pull Request #4267 · react/react-native-website · GitHub
Skip to content
Fix MDX double <p> tags#4267

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

 Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

 Merged

Simek
merged 1 commit into

from

Oct 10, 2024
 Merged


Fix MDX double <p> tags
#4267
Show file tree
Hide file tree
 Changes from all commits
Commits

Show all changes


1 commit


Select commit


File filter

Filter by extension
Filter by extension
Conversations

Failed to load comments. 
Loading
Jump to

Jump to file


Failed to load files. 
Loading
 Diff view

 Diff view


4 changes: 1 addition & 3 deletions
docs/appregistry.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: AppRegistry

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.
 </p>
 <p>If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.</p>
</div>

`AppRegistry` is the JS entry point to running all React Native apps. App root components should register themselves with `AppRegistry.registerComponent`, then the native system can load the bundle for the app and then actually run the app when it's ready by invoking `AppRegistry.runApplication`.
Expand Down

4 changes: 1 addition & 3 deletions
docs/debugging-native-code.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import con

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.</p>
</div>

## Accessing Logs
Expand Down

4 changes: 1 addition & 3 deletions
docs/linking.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -30,9 +30,7 @@ As mentioned in the introduction, there are some URL schemes for core functional

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.</p>
</div>

If you want to enable deep links in your app, please read the below guide:
Expand Down

4 changes: 1 addition & 3 deletions
docs/permissionsandroid.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: PermissionsAndroid

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.</p>
</div>

`PermissionsAndroid` provides access to Android M's new permissions model. The so-called "normal" permissions are granted by default when the application is installed as long as they appear in `AndroidManifest.xml`. However, "dangerous" permissions require a dialog prompt. You should use this module for those permissions.
Expand Down

4 changes: 1 addition & 3 deletions
docs/pushnotificationios.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ title: '🚧 PushNotificationIOS'

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.</p>
</div>

Handle notifications for your app, including scheduling and permissions.
Expand Down

18 changes: 4 additions & 14 deletions
website/blog/2020-07-06-version-0.63.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -61,9 +61,7 @@ import {Pressable, Text} from 'react-native';
</Pressable>;
```

<p className="snippet-caption">
 A simple example of a Pressable component in action
</p>
<p className="snippet-caption">A simple example of a Pressable component in action</p>

You can learn more about it from [the documentation](https://reactnative.dev/docs/pressable).

Expand All@@ -85,10 +83,7 @@ import {Text, PlatformColor} from 'react-native';
</Text>;
```

<p className="snippet-caption">
 Sets the color of the Text component to labelColor as defined by
 iOS.
</p>
<p className="snippet-caption">Sets the color of the Text component to labelColor as defined by iOS.</p>

Android, on the other hand, [provides colors like colorButtonNormal](https://developer.android.com/reference/android/R.attr#colorButtonNormal). You can use this color in React Native with:

Expand All@@ -103,10 +98,7 @@ import {View, Text, PlatformColor} from 'react-native';
</View>;
```

<p className="snippet-caption">
 Sets the background color of the View component to
 colorButtonNormal as defined by Android.
</p>
<p className="snippet-caption">Sets the background color of the View component to colorButtonNormal as defined by Android.</p>

You can learn more about `PlatformColor` from [the documentation](https://reactnative.dev/docs/platformcolor). You can also check the actual [code examples present in the RNTester](https://github.com/facebook/react-native/blob/master/packages/rn-tester/js/examples/PlatformColor/PlatformColorExample.js).

Expand All@@ -125,9 +117,7 @@ const customDynamicTextColor = DynamicColorIOS({
</Text>;
```

<p className="snippet-caption">
 Changes the text color based on the system theme
</p>
<p className="snippet-caption">Changes the text color based on the system theme</p>

You can learn more about `DynamicColorIOS` from [the documentation](https://reactnative.dev/docs/dynamiccolorios).

Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.70/appregistry.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: AppRegistry

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.
 </p>
 <p>If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.</p>
</div>

`AppRegistry` is the JS entry point to running all React Native apps. App root components should register themselves with `AppRegistry.registerComponent`, then the native system can load the bundle for the app and then actually run the app when it's ready by invoking `AppRegistry.runApplication`.
Expand Down

6 changes: 2 additions & 4 deletions
website/versioned_docs/version-0.70/debugging.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -164,10 +164,8 @@ You can view installation instructions [in the README](https://github.com/infini
# Native Debugging

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.
 </p>
 <h3>Projects with Native Code Only</h3><p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.</p>
</div>

## Accessing console logs
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.70/linking.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -30,9 +30,7 @@ As mentioned in the introduction, there are some URL schemes for core functional

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.</p>
</div>

If you want to enable deep links in your app, please read the below guide:
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.70/permissionsandroid.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import con

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.</p>
</div>

`PermissionsAndroid` provides access to Android M's new permissions model. The so-called "normal" permissions are granted by default when the application is installed as long as they appear in `AndroidManifest.xml`. However, "dangerous" permissions require a dialog prompt. You should use this module for those permissions.
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.70/pushnotificationios.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ title: '🚧 PushNotificationIOS'

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.</p>
</div>

Handle push notifications for your app, including permission handling and icon badge number.
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.71/appregistry.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: AppRegistry

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.
 </p>
 <p>If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.</p>
</div>

`AppRegistry` is the JS entry point to running all React Native apps. App root components should register themselves with `AppRegistry.registerComponent`, then the native system can load the bundle for the app and then actually run the app when it's ready by invoking `AppRegistry.runApplication`.
Expand Down

6 changes: 2 additions & 4 deletions
website/versioned_docs/version-0.71/debugging.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -164,10 +164,8 @@ You can view installation instructions [in the README](https://github.com/infini
# Native Debugging

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.
 </p>
 <h3>Projects with Native Code Only</h3><p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.</p>
</div>

## Accessing console logs
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.71/linking.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -30,9 +30,7 @@ As mentioned in the introduction, there are some URL schemes for core functional

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.</p>
</div>

If you want to enable deep links in your app, please read the below guide:
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.71/permissionsandroid.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import con

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.</p>
</div>

`PermissionsAndroid` provides access to Android M's new permissions model. The so-called "normal" permissions are granted by default when the application is installed as long as they appear in `AndroidManifest.xml`. However, "dangerous" permissions require a dialog prompt. You should use this module for those permissions.
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.71/pushnotificationios.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ title: '🚧 PushNotificationIOS'

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.</p>
</div>

Handle push notifications for your app, including permission handling and icon badge number.
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.72/appregistry.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: AppRegistry

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.
 </p>
 <p>If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.</p>
</div>

`AppRegistry` is the JS entry point to running all React Native apps. App root components should register themselves with `AppRegistry.registerComponent`, then the native system can load the bundle for the app and then actually run the app when it's ready by invoking `AppRegistry.runApplication`.
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.72/linking.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -30,9 +30,7 @@ As mentioned in the introduction, there are some URL schemes for core functional

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.</p>
</div>

If you want to enable deep links in your app, please read the below guide:
Expand Down

6 changes: 2 additions & 4 deletions
website/versioned_docs/version-0.72/native-debugging.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -6,10 +6,8 @@ title: Native Debugging
import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import constants from '@site/core/TabsConstants';

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.
 </p>
 <h3>Projects with Native Code Only</h3><p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.</p>
</div>

## Accessing native logs
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.72/permissionsandroid.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -5,9 +5,7 @@ title: PermissionsAndroid

<div className="banner-native-code-required">
 <h3>Project with Native Code Required</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.</p>
</div>

`PermissionsAndroid` provides access to Android M's new permissions model. The so-called "normal" permissions are granted by default when the application is installed as long as they appear in `AndroidManifest.xml`. However, "dangerous" permissions require a dialog prompt. You should use this module for those permissions.
Expand Down

4 changes: 1 addition & 3 deletions
website/versioned_docs/version-0.72/pushnotificationios.md

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,7 @@ title: '🚧 PushNotificationIOS'

<div className="banner-native-code-required">
 <h3>Projects with Native Code Only</h3>
 <p>
 The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.
 </p>
 <p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.</p>
</div>

Handle push notifications for your app, including permission handling and icon badge number.
Expand Down
Loading