Skip to content

Commit 76ba1dd

Browse files
committed
Refine format to use Unicode
1 parent 8e456e1 commit 76ba1dd

File tree

1 file changed

+12
-3
lines changed

1 file changed

+12
-3
lines changed

media/RenameDisclaimer.txt

Lines changed: 12 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,18 @@
1-
### PowerShell Extension Rename Disclaimer ###
1+
⚠️⚠️⚠️ PowerShell Extension Rename Disclaimer ⚠️⚠️⚠️
22

33
PowerShell is not a statically typed language. As such, the renaming of functions, parameters, and other symbols can only be done on a best effort basis. While this is sufficient for the majority of use cases, it cannot be relied upon to find all instances of a symbol and rename them across an entire code base such as in C# or TypeScript.
44

55
There are several edge case scenarios which may exist where rename is difficult or impossible, or unable to be determined due to the dynamic scoping nature of PowerShell.
66

7-
# Known Rename Limitations
7+
🤚🤚 Unsupported Scenarios
88

9-
- Renaming can only be done within a single file. Renaming symbols across multiple files is not supported.
9+
❌ Renaming can only be done within a single file. Renaming symbols across multiple files is not supported.
10+
11+
👍👍 Implemented and Tested Rename Scenaiors
12+
13+
See the supported rename scenarios we are currently testing at:
14+
https://github.com/PowerShell/PowerShellEditorServices/blob/main/test/PowerShellEditorServices.Test.Shared/Refactoring
15+
16+
📄📄 Filing a Rename Issue
17+
18+
If there is a rename scenario you feel can be reasonably supported in PowerShell, please file a bug report in the PowerShellEditorServices repository with the "Expected" and "Actual" being the before and after rename. We will evaluate it and accept or reject it and give reasons why. Items that fall under the Unsupported Scenarios above will be summarily rejected, however that does not mean that they may not be supported in the future if we come up with a reasonably safe way to implement a scenario.

0 commit comments

Comments
 (0)