@atlassian/clientside-extensions-docs 2.4.1-docs-1 → 2.4.1-docs-2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/content/server/framework/clientside-extensions/guides/how-to/debugging-and-troubleshooting-an-extension/abd-finding-web-resource.jpg +0 -0
- package/content/server/framework/clientside-extensions/guides/how-to/debugging-and-troubleshooting-an-extension.md +4 -4
- package/package.json +1 -1
- package/content/server/framework/clientside-extensions/guides/how-to/debugging-and-troubleshooting-an-extension/asd-finding-web-resource.png +0 -0
|
Binary file
|
|
@@ -4,7 +4,7 @@ platform: server
|
|
|
4
4
|
product: clientside-extensions
|
|
5
5
|
category: devguide
|
|
6
6
|
subcategory: how-to
|
|
7
|
-
date: '
|
|
7
|
+
date: '2022-01-04'
|
|
8
8
|
---
|
|
9
9
|
|
|
10
10
|
# Debugging and troubleshooting an extension
|
|
@@ -55,16 +55,16 @@ If you haven't found the plugin on the list, you should try checking and inspect
|
|
|
55
55
|
|
|
56
56
|
Now that you know your plugin was loaded, you can check if the extension was loaded on the page.
|
|
57
57
|
|
|
58
|
-
1. Install the **[
|
|
58
|
+
1. Install the **[Atlassian Browser DevTools Chrome extension](https://chrome.google.com/webstore/detail/atlassian-server-devtools/ifdlelpkchpppgmhmidenfmlhdafbnke)**. Open a web browser, turn on the DevTools and select the **ABD** tab.
|
|
59
59
|
2. Navigate to the page where you should see the extension point.
|
|
60
60
|
3. If the extension point is located in a different tab, e.g. Diff tab, select this tab on the page.
|
|
61
|
-
4. Now, in the DevTools window, select the **
|
|
61
|
+
4. Now, in the DevTools window, select the **ABD** tab and choose the **WRM Inspector** option.
|
|
62
62
|
5. The **WRM inspector** allows you to see a list of all the web-resources loaded on the page. To filter the list and find a web-resource with your extension code:
|
|
63
63
|
|
|
64
64
|
- Click on the **All context** option and select the name of the extension point
|
|
65
65
|
- In the **Filter** field, type in part of your plugin name
|
|
66
66
|
|
|
67
|
-

|
|
68
68
|
|
|
69
69
|
6. If you can find your web-resource on the list, it means that your extension was configured correctly, and it can be loaded on the page.
|
|
70
70
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@atlassian/clientside-extensions-docs",
|
|
3
|
-
"version": "2.4.1-docs-
|
|
3
|
+
"version": "2.4.1-docs-2",
|
|
4
4
|
"description": "Holds the official documentation for Altassian Server client-side extensions API.",
|
|
5
5
|
"license": "BSD-3-Clause",
|
|
6
6
|
"homepage": "https://bitbucket.org/atlassian/atlassian-clientside-extensions#readme",
|