From 14d07f539a2073f167203bbf08ecfcea4b851e62 Mon Sep 17 00:00:00 2001 From: Ash Date: Tue, 14 Jul 2020 16:19:20 -0400 Subject: [PATCH] Fixing debugging info for Windows. Also closes #207 #208 #182. --- CONTRIBUTING.md | 2 +- reference/core/apis.md | 2 +- reference/structure/manifest.md | 2 +- reference/uxp/storage-index.md | 2 +- reference/xd-index.md | 2 +- tutorials/debugging/index.md | 2 +- 6 files changed, 6 insertions(+), 6 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index a14f2d2ce..977d03bbc 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -59,7 +59,7 @@ When you're done making changes: ```bash # Rebuild HTML content - npm run test:404 +npm run book:build # Check for 404s npm run test:404 # See notes below about this diff --git a/reference/core/apis.md b/reference/core/apis.md index ee63a0475..a29559ddb 100644 --- a/reference/core/apis.md +++ b/reference/core/apis.md @@ -18,7 +18,7 @@ Read below for **how to access** XD and UXP APIs... ## XD-specific APIs -Most XD APIs are accessed by loading a module via `require()`, but some are passed directly to your plugin's handler functions. +Most XD APIs are accessed by loading a module via `require()`, but some are passed directly to your plugin's handler functions. See the [XD specific APIs page](../xd-index.md) for a full list of modules. Below are some examples of modules available via the API: * [selection](../selection.md) - Indicates the selected nodes and related context * This object is passed as an argument to your command handler function (see above) diff --git a/reference/structure/manifest.md b/reference/structure/manifest.md index d65e54140..2e21f0e33 100644 --- a/reference/structure/manifest.md +++ b/reference/structure/manifest.md @@ -90,7 +90,7 @@ Keyboard shortcuts are defined separately for each platform. Each definition is ## Menu Localization -Plugin menu item labels or panel labels can be localized to match XD's current UI language setting. Other manifest fields such as `name` and `description` _cannot be localized yet._ +Plugin menu item labels or panel labels can be localized to match XD's current UI language setting. Other manifest fields such as `name` _cannot be localized yet._ Localized labels are represented as an object containing multiple translations, instead of a single string value: diff --git a/reference/uxp/storage-index.md b/reference/uxp/storage-index.md index c004545e6..41b60b0fe 100644 --- a/reference/uxp/storage-index.md +++ b/reference/uxp/storage-index.md @@ -47,7 +47,7 @@ await anotherFile.write(contents); You can create new files inside a folder you have access to: ```js -const newFile = await folder.createEntry("examples.txt", {overwrite: true}); +const newFile = await folder.createFile("examples.txt", {overwrite: true}); newFile.write("Hello, world!"); ``` diff --git a/reference/xd-index.md b/reference/xd-index.md index d69f6f32d..1eaf7d3f8 100644 --- a/reference/xd-index.md +++ b/reference/xd-index.md @@ -1,4 +1,4 @@ -# XD specifics APIs +# XD specific APIs XD specific APIs enable developers to extend XD specific features. Using these APIs, developers can create plugins that create, read, update, and delete objects inside XD documents. Also, most other features available in XD, such as creating renditions, modifying assets panel, getting prototype data, conducting commands, and others are also available through these APIs. diff --git a/tutorials/debugging/index.md b/tutorials/debugging/index.md index c70a2f97e..02dc75de1 100644 --- a/tutorials/debugging/index.md +++ b/tutorials/debugging/index.md @@ -62,7 +62,7 @@ Navigate to the root folder of your plugin and **create a `debug.json` file**: ### 2. Launch Chrome DevTools -1. Windows only: _before_ launching XD, open an admin command prompt and run `CheckNetIsolation LoopbackExempt -is -n="Adobe.CC.XD.adky2gkssdxte"` -- do this _each time_ you want to debug a plugin. +1. Windows only: _before_ launching XD, open an admin command prompt and run `CheckNetIsolation LoopbackExempt -is -n="Adobe.CC.XD_adky2gkssdxte"` -- do this _each time_ you want to debug a plugin. 2. Open Google Chrome and navigate to **`chrome://inspect`** _(you must use Chrome)_ 3. One-time setup: ensure "Discover Network Targets" is enabled. Click the Configure button next to this and add `localhost:9345` (or whatever port number your `debug.json` file used). 4. Click the "inspect" link under your plugin's ID.