main

Author: sharpchen

docs/document/Powershell/docs/Alias.md

@@ -6,15 +6,21 @@
 New-Alias <alias> <cmd_name>
 ```
 
+> [!TIP]
+> Use `nal` alias for `New-Alias`.
+
 > [!note]
-> `New-Alias` throws when the alias already exist while `Set-Alias` will overrides it.
+> `New-Alias` throws when the alias already exist while `Set-Alias` will override it.
 
 ## Override an Alias
 
 ```ps1
 Set-Alias <alias> <cmd_name>
 ```
 
+> [!TIP]
+> Use `sal` alias for `Set-Alias`.
+
 ## Checkout Alias
 
 - Check out by alias
@@ -23,6 +29,9 @@ Set-Alias <alias> <cmd_name>
 Get-Alias <alias>
 ```
 
+> [!TIP]
+> Use `gal` alias for `Get-Alias`.
+
 Or use `Get-Command`
 
 ```ps1
@@ -61,6 +70,10 @@ alias gl='git log' # fine
 New-Alias gl 'git log' # not allowed! # [!code error] 
 ```
 
-> [!TIP]
-> Use functions to do alias with predetermined parameters in your profile.
+Should use function instead.
 
+```ps1
+function gl {
+    git log
+}
+```

docs/document/Powershell/docs/File System/2.Working Directory.md

@@ -27,7 +27,7 @@ There's two ways to get current working directory in Powershell.
   - `pwd` is an builtin alias for `Get-Location`.
 
 ```ps1
-(Get-Location).Path # equivalent to $pwd
+(Get-Location).Path # equivalent to $pwd.Path
 ```
 
 ```console

…t/Powershell/docs/Language/Evaluation.md …t/Powershell/docs/Language/Expression.mddocs/document/Powershell/docs/Language/Evaluation.md renamed to docs/document/Powershell/docs/Language/Expression.md docs/document/Powershell/docs/Language/Evaluation.md renamed to docs/document/Powershell/docs/Language/Expression.md

@@ -0,0 +1,9 @@
+# Operators
+
+## Keyword Operator
+
+| Desc | Operator | Example | Reference |
+| --------------- | --------------- | --------------- |--------------- |
+| Split a string by separator into a `string[]`| `-split` | `'1,2,3' -split ','` | [about_Split](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_split?view=powershell-7.4)  |
+| Item1.2 | Item2.2 | Item3.2 | |
+

docs/document/Powershell/docs/Language/Operators.md

@@ -2,8 +2,112 @@
 
 ## String Interpolation
 
+Interpolated string should quote with `"`.
+
+Use `$` to interpolate:
+- variable
+- expression
+- member accessing
+
+```ps1
+"Profile Path: $Profile" # variable
+"1 + 1 = $(1 + 1)" # expression
+
+# functionaly identical
+"cwd: $($pwd.Path)" # Member accessing
+"cwd: $pwd"
+
+"$(@(1, 2, 3)[0])"
+```
+
+> [!NOTE]
+> `$()` is being called **SubExpression Operator** in Powershell.
+
+## Verbatim String
+
+Verbatim string should quote with `'`.
+Can contains new lines and 
+
+```ps1
+'
+    It''s a verbatim string! 
+    and this is a new line!
+'
+```
+
+> [!NOTE]
+> Verbatim string does not allow interpolation in Powershell which differs from `C#`.
+
 ## Raw String
 
+> [!NOTE]
+> Raw string is being called **Here String** in Powershell.
+
+**Here String** typically allows string contents starting at the second line and truncates the last newline.
+
+Use `@'...'@` or `@"..."@` to present Verbatim Here String or Interpolated Here String.
+
+```ps1
+@"
+    <foo>$Profile</foo>
+"@
+
+@'
+    {
+        "foo": {
+            "bar": []
+        }
+    }
+'@
+```
+
+> [!NOTE]
+> You can have quotation mark `"` in `@"..."@` and for `'` respectively.
+
 ## String Concatenation
 
+Use `+`
+
 ## Character Escaping
+
+### Quotation Mark
+
+Use double `"` to escape `"` in a interpolated string.
+
+```ps1
+"""""" # ""
+"I quote, ""haha!""" # I quote, "haha!"
+```
+
+Or use `` ` `` to escape the same quotation mark in the containing quotation.
+
+```ps1
+"I quote, `"haha!`""
+```
+
+Use double `'` to escape `'` in a verbatim string.
+
+```ps1
+'''''' # ''
+'I quote, ''haha!''' # I quote, 'haha!'
+```
+
+> [!NOTE]
+> See [about_Specical_Characters](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_special_characters?view=powershell-7.4) 
+
+## Split & Join
+
+## Format String
+
+## String Evaluation in Interpolation
+
+### Collection
+
+Collections like Array and HashTable are formatted by certain separator defined by `$OFS`(Output Field Separator)
+
+```ps1
+"$(1, 2, 3)" # 1 2 3
+```
+
+> [!NOTE]
+> `$OFS` is not a builtin variable, you'll have to create it manually or pwsh uses space ` ` as the separator.

docs/document/Powershell/docs/Language/String.md

@@ -0,0 +1,14 @@
+# Variable
+
+## Declaration & Reference
+
+Variable declaration and variable referencing shares a identical syntax.
+
+Variable name must starts with `$` but `$` is not part of the name.
+
+```ps1
+$var = 'foo'
+echo $var
+```
+
+## Scope

docs/document/Powershell/docs/Language/Variable.md

@@ -4,6 +4,6 @@ Powershell is a Object-Oriented shell language, so inspection and manipulation o
 
 This section focuses on how to work with objects, including:
 
-- LINQ like transformation over objects.(including usage of `.NET` LINQ in Powershell)
 - Object comparison.
-- Serialization and Deserialization.
+- LINQ like transformation over objects.(including usage of `.NET` LINQ in Powershell)
+- Understanding `PSObject`, ETS(Extended Type System), member manipulation and inspection.

docs/document/Powershell/docs/Object Manipulation/1.Overview.md

@@ -0,0 +1,29 @@
+# Extended Type System
+
+Extended Type System(ETS) is for consistent experience with **some** `.NET` types when working with Powershell.
+
+For this purpose, Powershell wraps the traget object as `PSObject` with two approaches:
+
+- Set the object to be wrapped as a meta object(similar to lua metatable)
+- Add extra members to the containing `PSObject` itself.
+
+A common example would be `Process` type.
+
+```ps1
+(gps | select -First 1).GetType().Name # Process
+(gps | select -First 1) -is [PSObject] # True
+(gps | select -First 1) -is [PSCustomObject] # True
+# -is checks underlying type too
+(gps | select -First 1) -is [System.Diagnostics.Process] # True
+```
+
+The functionality of ETS achieved benifits:
+
+- Allow custom behaviours like formatting, sorting for your custom type or object.
+- Dynamic interpreting a `HashTable` to any `PSObject`
+- Accessibility to the underlying object.
+- Manipulation on extended members.
+
+## ETS Members
+
+

docs/document/Powershell/docs/Object Manipulation/Extended Type System.md

@@ -0,0 +1,30 @@
+# ForEach
+
+> [!TIP]
+> Use `foreach` or `%` alias for `ForEach-Object`.
+
+## Works like Select
+
+`ForEach-Object` can do the same thing as `Select-Object -ExpandProperty`.
+
+```ps1
+gci | foreach Name
+# or
+gci | foreach { $_.Name }
+# equivalent to 
+gci | select -ExpandProperty Name
+```
+
+The way `ForEach-Object` behaves is collecting implicitly returned values as an array. Every implicitly returned value will be collected as a item.
+
+```ps1
+gci | foreach { $_.Exists, $false } # True, False, True, False...
+```
+
+If you do want a `$null` return, use `Out-Null` to swallow the value.
+
+```ps1
+# doesn't make much sense though
+(gci | foreach { $_.Name | Out-Null }) -eq $null # True
+```
+