chore: cleanup and lint (#338)

- Remove accidental `yarn.lock` files.
- Correct package.json dependencies
- run prettier on files.
- Add samples for Arabic

Author: Jason3S

CODE_OF_CONDUCT.md

@@ -17,23 +17,23 @@ diverse, inclusive, and healthy community.
 Examples of behavior that contributes to a positive environment for our
 community include:
 
-* Demonstrating empathy and kindness toward other people
-* Being respectful of differing opinions, viewpoints, and experiences
-* Giving and gracefully accepting constructive feedback
-* Accepting responsibility and apologizing to those affected by our mistakes,
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,
   and learning from the experience
-* Focusing on what is best not just for us as individuals, but for the
+- Focusing on what is best not just for us as individuals, but for the
   overall community
 
 Examples of unacceptable behavior include:
 
-* The use of sexualized language or imagery, and sexual attention or
+- The use of sexualized language or imagery, and sexual attention or
   advances of any kind
-* Trolling, insulting or derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or email
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email
   address, without their explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
+- Other conduct which could reasonably be considered inappropriate in a
   professional setting
 
 ## Enforcement Responsibilities
@@ -106,7 +106,7 @@ Violating these terms may lead to a permanent ban.
 ### 4. Permanent Ban
 
 **Community Impact**: Demonstrating a pattern of violation of community
-standards, including sustained inappropriate behavior,  harassment of an
+standards, including sustained inappropriate behavior, harassment of an
 individual, or aggression toward or disparagement of classes of individuals.
 
 **Consequence**: A permanent ban from any sort of public interaction within

dict-extensions.code-workspace

@@ -3,6 +3,9 @@
         {
             "path": "."
         },
+        {
+            "path": "extensions/arabic"
+        },
         {
             "path": "extensions/bulgarian"
         },

extensions/arabic/.vscode/launch.json

@@ -7,21 +7,21 @@
             "type": "extensionHost",
             "request": "launch",
             "runtimeExecutable": "${execPath}",
-            "args": ["--extensionDevelopmentPath=${workspaceRoot}" ],
+            "args": ["--extensionDevelopmentPath=${workspaceRoot}", "${workspaceRoot}/samples"],
             "stopOnEntry": false,
             "sourceMaps": true,
-            "outFiles": [ "${workspaceRoot}/out/src/**/*.js" ],
+            "outFiles": ["${workspaceRoot}/out/src/**/*.js"],
             "preLaunchTask": "npm: build"
         },
         {
             "name": "Launch Tests",
             "type": "extensionHost",
             "request": "launch",
             "runtimeExecutable": "${execPath}",
-            "args": ["--extensionDevelopmentPath=${workspaceRoot}", "--extensionTestsPath=${workspaceRoot}/out/test" ],
+            "args": ["--extensionDevelopmentPath=${workspaceRoot}", "--extensionTestsPath=${workspaceRoot}/out/test"],
             "stopOnEntry": false,
             "sourceMaps": true,
-            "outFiles": [ "${workspaceRoot}/out/test/**/*.js" ],
+            "outFiles": ["${workspaceRoot}/out/test/**/*.js"],
             "preLaunchTask": "npm: build"
         }
     ]

extensions/arabic/.vscode/tasks.json

@@ -32,9 +32,7 @@
             "label": "npm: watch",
             "type": "npm",
             "script": "watch",
-            "problemMatcher": [
-                "$tsc-watch"
-            ]
+            "problemMatcher": ["$tsc-watch"]
         }
     ]
 }

extensions/arabic/README.md

@@ -4,22 +4,22 @@ Arabic dictionary extension for VS Code.
 
 Imports the Arabic spell checking dictionary for [Code Spell Checker](https://marketplace.visualstudio.com/items?itemName=streetsidesoftware.code-spell-checker).
 
-
-
 ## Installation
 
 After this extension is installed, it is necessary to tell the spell checker to use it.
 
 ### Enable Dictionary
 
-Commands (use `F1` or *View -> Command Palette...*):
+Commands (use `F1` or _View -> Command Palette..._):
+
 - `F1` `Show Spell Checker Configuration Info`
 - Select the `Language` tab.
 - Enable the language Globally or in just the Workspace.
 
 ### Disable Dictionary
 
-Commands (use `F1` or *View -> Command Palette...*):
+Commands (use `F1` or _View -> Command Palette..._):
+
 - `F1` `Show Spell Checker Configuration Info`
 - Select the `Language` tab.
 - Disable the language Globally or in just the Workspace.
@@ -28,15 +28,15 @@ Commands (use `F1` or *View -> Command Palette...*):
 
 This is done with the `language` setting.
 
-*Preferences* -> *Settings*
+_Preferences_ -> _Settings_
 
 Adding `ar` to the `cSpell.language` setting, will enable the Arabic dictionary.
 Example using both English and Arabic dictionaries:
+
 ```javascript
 "cSpell.language": "en,ar",
 ```
 
-
-
 ## Requirements
+
 This extension will automatically include [Code Spell Checker](https://marketplace.visualstudio.com/items?itemName=streetsidesoftware.code-spell-checker) extension.

extensions/arabic/cspell-ext.json

@@ -1,5 +1,3 @@
 {
-    "import": [
-        "@cspell/dict-ar/cspell-ext.json"
-    ]
+    "import": ["@cspell/dict-ar/cspell-ext.json"]
 }

extensions/arabic/samples/.vscode/settings.json

@@ -0,0 +1,3 @@
+{
+    "cSpell.language": "en,ar"
+}

extensions/arabic/samples/README-ar.md

@@ -0,0 +1,17 @@
+2008-01-10
+السلام عليكم،
+
+تجدون رفقته ملفي قاموس التدقيق الإملائي للغة العربية hunspell-ar لمشروع آيسبل Ayaspell في نسخته النهائية (الملفان هما: ar.dic و ar.aff) اللذين يعملان ضمن برنامج هانسبل Hunspell (الإصدارة 1.1.12 وما فقوها) للمجموعة المكتبية أوبن-أوفيس OpenOffice.org.
+
+عند تنصيبكم واستعمالكم للقاموس فإن المؤلف لا يتحمل أية مسؤولية في حالة حصول إتلاف ملفات أو ظهور خلل في الجهاز ناتجين عن تنصيبه أو استعماله.
+يخضع قاموس آيسبل للرخص الثلاثية: GPL/LGPL/MPL.
+
+لمتابعة تطوير المشروع:
+القائمة البريدية: http://ayaspell.sourceforge.net
+المدونة: http://ayaspell.blogspot.com
+الموقع: http://ayaspell.sourceforge.net
+==========================================================================
+
+<!---
+cspell:ignore آيسبل أوفيس هانسبل
+--->

extensions/arabic/samples/cspell.json

@@ -0,0 +1,6 @@
+{
+    "words": [
+        "Ayaspell",
+        "myspell"
+    ]
+}

extensions/arabic/samples/install-ar.md

@@ -0,0 +1,44 @@
+    *  التنصيب على نظام لينكس
+    * التنصيب على نظام ويندوز
+    * التنصيب على نظام ماكنتوش
+
+1 - توظيف قاموس التدقيق الإملائي تحت نظام لينكس
+
+---
+
+كيفية تنصيب وتوظيف المدقق الإملائي الاختباري على محرر المجموعة الكتبية أوبن - أوفيس OpenOffice.org تحت نظام لينكس Gnu/Linux:
+
+- أولاً: تفعيل التدقيق إملائي لأية لغة تريد على أوبن-أوفيس حتى تُنشط خاصية المدقق الإملائي وتُحمّل المركبات والبرامج الضرورية له.
+- ثانياً: من اللازم إغلاق Openoffice.org إن كان مشغلاً و إبطال عمل برنامج تسريع عمل OpenOffice.org المسمى Quicks tarter إن كان منشطاً من قبل على نظامك.
+- ثالثاً: نسخ الملفين ar.dic و ar.aff في الدليل /usr/share/myspell/dicts/
+  cp ar.dic /usr/share/myspell/dicts/
+  cp ar.aff /usr/share/myspell/dicts/
+
+- رابعاً: تحرير etc/openoffice/dictionary.lst/ بإضافة السطر الآتي(لا تنسى حفظ الأصلي للاحتياط):
+  DICT ar TN ar
+- خامساً: شغّل برنامج أوبن - أوفيس ثم من خلال الإعدادات (أدوات ثم خيارات/إعدادات لغوية) قم بتعيين اللغة المراد تدقيق إملائها: عربية (تونس) في المثال.
+
+2 - توظيف قاموس التدقيق الإملائي تحت نظام ويندوز
+
+---
+
+كيفية تنصيب وتوظيف المدقق الإملائي الاختباري على محرر المجموعة الكتبية أوبن - أوفيس OpenOffice.org تحت نظام لينكس Windows:
+
+- أولاً: تفعيل التدقيق إملائي لأية لغة تريد على أوبن-أوفيس حتى تنشط خاصية المدقق الإملائي وتحمل المركبات والبرامج الضرورية له.
+- ثانياً: من اللازم إغلاق Openoffice.org إن كان مشغلاً و إبطال عمل برنامج تسريع عمل OpenOffice.org المسمى Quick starter إن كان منشطاً من قبل على نظامك.
+- ثالثاً: نسخ الملفين ar.dic و ar.aff في الدليل
+  \Program Files\OpenOffice.org 2.1\share\dict\ooo
+
+- رابعاً: تحرير \Program Files\OpenOffice.org 2.1\share\dict\ooodictionary.lst بإضافة السطر الآتي مثلاً (لا تنسى حفظ الأصلي للاحتياط):
+  DICT ar TN ar
+- خامساً: شغّل برنامج أوبن - أوفيس ثم من خلال الإعدادات (أدوات ثم خيارات/إعدادات لغوية) ثم قم بتعيين اللغة المراد تدقيق إملائها: عربية (تونس) في المثال.
+
+3 - توظيف قاموس التدقيق الإملائي تحت نظام ماكنتوش
+
+---
+
+ليس لدي نظام ماكنتوش لمعرفة كيفية التنصيب! من كان يعرف ليتصل بي كي أضيف المعلومة عل هذه الصفحة. وشكراً :)
+
+<!---
+cspell:ignore ooodictionary أوفيس تُنشط شغّل ماكنتوش وتُحمّل ويندوز
+--->

extensions/arabic/src/extension.ts

@@ -8,37 +8,38 @@ interface CodeSpellCheckerExtension {
     disableLocale(isGlobal: boolean, locale: string): Promise<void>;
 }
 
-// 
+//
 const locale = 'ar';
-// 
+//
 
 // this method is called when your extension is activated
 // your extension is activated the very first time the command is executed
 export function activate(context: vscode.ExtensionContext) {
-
     const vscodeSpellCheckerExtension = 'streetsidesoftware.code-spell-checker';
     const configLocation = context.asAbsolutePath('./cspell-ext.json');
 
     const extension = vscode.extensions.getExtension<CodeSpellCheckerExtension>(vscodeSpellCheckerExtension);
 
     if (extension) {
-        extension.activate().then(ext => {
+        extension.activate().then((ext) => {
             // We need to register the dictionary configuration with the Code Spell Checker Extension
             ext?.registerConfig?.(configLocation);
         });
     }
 
-    // 
+    //
     function enable(isGlobal: boolean) {
-        extension && extension.activate().then(ext => {
-            ext?.enableLocale?.(isGlobal, locale);
-        });
+        extension &&
+            extension.activate().then((ext) => {
+                ext?.enableLocale?.(isGlobal, locale);
+            });
     }
 
     function disable(isGlobal: boolean) {
-        extension && extension.activate().then(ext => {
-            ext?.disableLocale?.(isGlobal, locale);
-        });
+        extension &&
+            extension.activate().then((ext) => {
+                ext?.disableLocale?.(isGlobal, locale);
+            });
     }
 
     // Push the disposable to the context's subscriptions so that the
@@ -47,11 +48,10 @@ export function activate(context: vscode.ExtensionContext) {
         vscode.commands.registerCommand('cSpellExt_arabic.enable', () => enable(true)),
         vscode.commands.registerCommand('cSpellExt_arabic.disable', () => disable(true)),
         vscode.commands.registerCommand('cSpellExt_arabic.enableWorkspace', () => enable(false)),
-        vscode.commands.registerCommand('cSpellExt_arabic.disableWorkspace', () => disable(false)),
+        vscode.commands.registerCommand('cSpellExt_arabic.disableWorkspace', () => disable(false))
     );
-    // 
+    //
 }
 
 // this method is called when your extension is deactivated
-export function deactivate() {
-}
+export function deactivate() {}

extensions/arabic/test/extension.test.ts

@@ -14,11 +14,10 @@ import * as myExtension from '../src/extension';
 */
 
 // Defines a Mocha test suite to group tests of similar kind together
-suite("Extension Tests", () => {
-
+suite('Extension Tests', () => {
     // Defines a Mocha unit test
-    test("Something 1", () => {
+    test('Something 1', () => {
         assert.equal(-1, [1, 2, 3].indexOf(5));
         assert.equal(-1, [1, 2, 3].indexOf(0));
     });
-});
+});

extensions/arabic/test/index.ts

@@ -15,8 +15,8 @@ var testRunner = require('vscode/lib/testrunner');
 // You can directly control Mocha options by uncommenting the following lines
 // See https://github.com/mochajs/mocha/wiki/Using-mocha-programmatically#set-options for more info
 testRunner.configure({
-    ui: 'tdd', 		// the TDD UI is being used in extension.test.ts (suite, test, etc.)
-    useColors: true // colored output from test results
+    ui: 'tdd', // the TDD UI is being used in extension.test.ts (suite, test, etc.)
+    useColors: true, // colored output from test results
 });
 
-module.exports = testRunner;
+module.exports = testRunner;

extensions/arabic/vsc-extension-quickstart.md

@@ -1,33 +1,38 @@
 # Welcome to your first VS Code Extension
 
 ## What's in the folder
-* This folder contains all of the files necessary for your extension
-* `package.json` - this is the manifest file in which you declare your extension and command.
-The sample plugin registers a command and defines its title and command name. With this information
-VS Code can show the command in the command palette. It doesn’t yet need to load the plugin.
-* `src/extension.ts` - this is the main file where you will provide the implementation of your command.
-The file exports one function, `activate`, which is called the very first time your extension is
-activated (in this case by executing the command). Inside the `activate` function we call `registerCommand`.
-We pass the function containing the implementation of the command as the second parameter to
-`registerCommand`.
+
+- This folder contains all of the files necessary for your extension
+- `package.json` - this is the manifest file in which you declare your extension and command.
+  The sample plugin registers a command and defines its title and command name. With this information
+  VS Code can show the command in the command palette. It doesn’t yet need to load the plugin.
+- `src/extension.ts` - this is the main file where you will provide the implementation of your command.
+  The file exports one function, `activate`, which is called the very first time your extension is
+  activated (in this case by executing the command). Inside the `activate` function we call `registerCommand`.
+  We pass the function containing the implementation of the command as the second parameter to
+  `registerCommand`.
 
 ## Get up and running straight away
-* press `F5` to open a new window with your extension loaded
-* run your command from the command palette by pressing (`Ctrl+Shift+P` or `Cmd+Shift+P` on Mac) and typing `Hello World`
-* set breakpoints in your code inside `src/extension.ts` to debug your extension
-* find output from your extension in the debug console
+
+- press `F5` to open a new window with your extension loaded
+- run your command from the command palette by pressing (`Ctrl+Shift+P` or `Cmd+Shift+P` on Mac) and typing `Hello World`
+- set breakpoints in your code inside `src/extension.ts` to debug your extension
+- find output from your extension in the debug console
 
 ## Make changes
-* you can relaunch the extension from the debug toolbar after changing code in `src/extension.ts`
-* you can also reload (`Ctrl+R` or `Cmd+R` on Mac) the VS Code window with your extension to load your changes
+
+- you can relaunch the extension from the debug toolbar after changing code in `src/extension.ts`
+- you can also reload (`Ctrl+R` or `Cmd+R` on Mac) the VS Code window with your extension to load your changes
 
 ## Explore the API
-* you can open the full set of our API when you open the file `node_modules/vscode/vscode.d.ts`
+
+- you can open the full set of our API when you open the file `node_modules/vscode/vscode.d.ts`
 
 ## Run tests
-* open the debug viewlet (`Ctrl+Shift+D` or `Cmd+Shift+D` on Mac) and from the launch configuration dropdown pick `Launch Tests`
-* press `F5` to run the tests in a new window with your extension loaded
-* see the output of the test result in the debug console
-* make changes to `test/extension.test.ts` or create new test files inside the `test` folder
-    * by convention, the test runner will only consider files matching the name pattern `**.test.ts`
-    * you can create folders inside the `test` folder to structure your tests any way you want
+
+- open the debug viewlet (`Ctrl+Shift+D` or `Cmd+Shift+D` on Mac) and from the launch configuration dropdown pick `Launch Tests`
+- press `F5` to run the tests in a new window with your extension loaded
+- see the output of the test result in the debug console
+- make changes to `test/extension.test.ts` or create new test files inside the `test` folder
+  - by convention, the test runner will only consider files matching the name pattern `**.test.ts`
+  - you can create folders inside the `test` folder to structure your tests any way you want