Skip to content

Commit a283c2f

Browse files
committed
Fixed react native docs for rst errors
1 parent d2ab38b commit a283c2f

File tree

1 file changed

+15
-6
lines changed

1 file changed

+15
-6
lines changed

docs/integrations/react-native.rst

Lines changed: 15 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -30,17 +30,27 @@ Now we need to set up Raven.js to use your Sentry DSN:
3030
.config('https://___PUBLIC_DSN___', { release: RELEASE_ID })
3131
.install();
3232
33-
RELEASE_ID is a string representing the “version” of the build you are about to distribute. This can be the SHA of your Git repository’s HEAD. It can also be a semantic version number (e.g. “1.1.2”), pulled from your project’s package.json file. More below.
33+
RELEASE_ID is a string representing the “version” of the build you are
34+
about to distribute. This can be the SHA of your Git repository’s HEAD. It
35+
can also be a semantic version number (e.g. “1.1.2”), pulled from your
36+
project’s package.json file. More below.
3437

3538
About Releases
3639
--------------
3740

38-
Every time you build and distribute a new version of your React Native app, you’ll want to create a new release inside Sentry. This is for two important reasons:
41+
Every time you build and distribute a new version of your React Native
42+
app, you’ll want to create a new release inside Sentry. This is for two
43+
important reasons:
3944

4045
- You can associate errors tracked by Sentry with a particular build
4146
- You can store your source maps generated for each build inside Sentry
4247

43-
Unlike a normal web application where your JavaScript files (and source maps) are served and hosted from a web server, your React Native code is being served from the target device’s filesystem. So you’ll need to upload both your **source code** AND **source maps** directly to Sentry, so that we can generate handy stack traces for you to browse when examining exceptions trigged by your application.
48+
Unlike a normal web application where your JavaScript files (and source
49+
maps) are served and hosted from a web server, your React Native code is
50+
being served from the target device’s filesystem. So you’ll need to upload
51+
both your **source code** AND **source maps** directly to Sentry, so that
52+
we can generate handy stack traces for you to browse when examining
53+
exceptions trigged by your application.
4454

4555

4656
Generating source maps
@@ -62,9 +72,8 @@ Then, in another tab, curl the packager service for your source map:
6272
6373
This will write a file index.ios.map to the current directory.
6474

65-
Lastly, you'll need to `create a new release and upload your source code files and source maps as release artifacts`_.
66-
67-
.. _create a new release and upload your source map as a release artifact: https://docs.getsentry.com/hosted/clients/javascript/sourcemaps/#uploading-source-maps-to-sentry
75+
Lastly, you'll need to `create a new release and upload your source code files and source maps as release artifact
76+
<https://docs.getsentry.com/hosted/clients/javascript/sourcemaps/#uploading-source-maps-to-sentry>`__.
6877

6978
Expanded Usage
7079
--------------

0 commit comments

Comments
 (0)