Squashed 'src/paratext-bible-word-list/' changes from 1c7c788..01213e7

01213e7 update `@sillsdev/scripture` (#74)
652c777 feat: added some fields to `manifest.json` and moved URL-related fields (#73)
8076b16 fix: changed elevatedPrivileges to an array
ccbf06c refactor: adjusted structure for fields in manifest.json
4df6936 feat: added 'moreInfoUrl' and 'supportUrl' to manifest

git-subtree-dir: src/paratext-bible-word-list
git-subtree-split: 01213e7e2372ab91e5ac17299cc531ec586048ae

README.md

@@ -44,6 +44,8 @@ To make the process of customizing from the template as smooth as possible, we r
 - In `assets/displayData.json`:
 
   - If your extension has an icon, update the `icon` value to point towards the icon file (for example: `assets/icon.svg`)
+  - Update the `moreInfoUrl` field to web URL to a page where users can find out more information about you / your organization / your extension.
+  - Update the `supportUrl` field to web URL to a support page where users can request help and report issues with your extension.
   - Update the `en` entry of `localizedDisplayInfo` so that:
 
     - `displayName` contains a human-readable name for your extension (i.e. `Your Extension Name`).

assets/displayData.json

@@ -1,5 +1,7 @@
 {
   "icon": "",
+  "moreInfoUrl": "",
+  "supportUrl": "",
   "localizedDisplayInfo": {
     "en": {
       "displayName": "Paranext Extension Template",

manifest.json

@@ -5,6 +5,8 @@
   "author": "Paranext",
   "license": "MIT",
   "main": "src/main.ts",
+  "extensionDependencies": {},
+  "elevatedPrivileges": [],
   "types": "src/types/paranext-extension-template.d.ts",
   "menus": "contributions/menus.json",
   "settings": "contributions/settings.json",

package.json

@@ -31,7 +31,7 @@
     "react-dom": ">=18.2.0"
   },
   "dependencies": {
-    "@sillsdev/scripture": "^2.0.0",
+    "@sillsdev/scripture": "^2.0.1",
     "platform-bible-utils": "file:../paranext-core/lib/platform-bible-utils"
   },
   "devDependencies": {