Skip to content

Commit 66882c9

Browse files
committed
apply review suggestion && adjust wording around backend fetching
1 parent a3c649f commit 66882c9

File tree

1 file changed

+6
-5
lines changed
  • src/includes/platforms/configuration/integrations

1 file changed

+6
-5
lines changed

src/includes/platforms/configuration/integrations/plugin.mdx

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -112,12 +112,13 @@ Available options:
112112

113113
### ContextLines
114114

115-
_Import name: `Sentry.Integrations.ReportingObserver`_
115+
_Import name: `Sentry.Integrations.ContextLines`_
116+
117+
This integration attaches source code of inline JavaScript inside the page's HTML (e.g. JS in `<script>` tags) to errors captured by the SDK.
118+
Note that this integration _cannot_ collect source code from assets referenced by your HTML (e.g. `<script src="..." />`).
116119

117-
This integration collects code lines at and around the stack frames of an error that point to code in the current page's html (for example in `<script>` tags).
118-
Note that this integration _cannot_ collect code lines from other files that are loaded by the browser.
119-
Generally, context line collection is already taken care of by the Sentry backend which will try to fetch the JavaScript file from your server when an error is reported to Sentry.
120-
However, in some cases, our backend might not be able to fetch the JavaScript file, for example if the file is only available for logged in users.
120+
Generally, the Sentry backend tries to attach source code to these errors by fetching the page and extracting the respective lines.
121+
However, in some cases, our backend might not be able to fetch the JavaScript file, for example if the file is only available for authenticated users.
121122

122123
Use this integration if you have inline JS code in HTML pages that can't be accessed by our backend, for example due to a login-protected page.
123124

0 commit comments

Comments
 (0)