main

Author: sharpchen

docs/document/Skill/Lua/docs/Coroutine.md

@@ -23,6 +23,8 @@ Thusly, one should never use words such as *thread* or *multi-threading* when in
     - returns `boolean` indicating whether resume succeeded and `...any` returned from the resumed coroutine by `coroutine.yield`.
     - supports passing args to the wrapped function of the coroutine
 - `coroutine.wrap(fn: function): function`: wrap resumption as a capsulated function for simplicity.
+- `coroutine.running(): thread, boolean`: returns current running coroutine object, particularly used to re-access self reference of a coroutine inside the function body.
+    - `boolean` indicates the returned thread is main thread or not
 
 ## Coordination
 
@@ -137,3 +139,5 @@ nxt = consume()
 >  end
 >end
 >```
+
+

docs/document/Skill/PowerShell/docs/Modulization/1.Overview.md

@@ -0,0 +1,45 @@
+# Overview
+
+## Filetypes
+
+- `.ps1`: general powershell script
+- `.psm1`: powershell module file
+- `.psd1`: powershell module manifest
+
+## Module Structure
+
+- `<modname>.psm1`: the module entry file at module root, **should have the same name as parent folder**.
+- `<modname>.psd1`(optional): the module manifest at module root containing module description such as `Author`, `Version` and so on.
+- `*.ps1`: arbitrary scripts that can be sourced in `<modname>.psm1`
+    - you can place such scripts in any manner since they wouldn't be executed unless you source it the module entry `.psm1` manually.
+
+## Search Path
+
+`$env:PSModulePath` stores one or more paths to search module on any `*-Module` operation.
+Each folder added should be a parent containing module folders.
+
+```
+./YourModules/
+├── InvokeBuild
+├── platyPS
+├── ...
+└── PSFzf
+```
+
+To add your own module path, use:
+```ps1
+$env:PSModulePath += "$([IO.Path]::PathSeparator)$customModulePath"
+```
+
+## Member Exporting
+
+- Explicit `Export-ModuleMember` within `*.psm1` file only.
+- Implicit exporting when `Export-ModuleMember` is not used
+    - all functions and aliases are exported
+    - other member are hidden inside module
+
+> [!NOTE]
+> See: [Export-ModuleMember](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/export-modulemember?view=powershell-7.5) 
+
+> [!TIP]
+> Using explicit `Export-ModuleMember` is always the best practice.

docs/services/DocumentService.ts

@@ -29,7 +29,7 @@ export const skillDocMap = {
   'Entity Framework Core': { icon: '🗿', description: '' },
   // 'HTML & CSS': { icon: '😬', description: '' },
   PowerShell: { icon: '🐚', description: 'A pretty solid shell' },
-  Lua: { icon: '🌝', description: 'I wish lua could have JavaScript syntax' },
+  Lua: { icon: '🌝', description: '' },
 } as const satisfies DocumentInfo;
 
 const readingDocMap = {