Skip to content

Commit 36c5e98

Browse files
committed
Add a 5.0 release message
1 parent e4c77bb commit 36c5e98

File tree

2 files changed

+38
-0
lines changed

2 files changed

+38
-0
lines changed

messages.json

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,5 @@
11
{
2+
"5.0.0": "messages/5.0.0.md",
23
"5.0.0-beta.01": "messages/5.0.0-beta.md",
34
"4.2.0": "messages/5.0.0-prerelease-invitation.md",
45
"3.1.1": "messages/4.0.0-prerelease-invitation.md"

messages/5.0.0.md

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
# 5.0.0
2+
3+
This is a large syntax change with substantial modification
4+
to where some keywords are able to be used.
5+
6+
If you find bugs, especially egregious ones that break code
7+
highlighting further down in the file, please mention them at
8+
https://github.com/SublimeText/PowerShell/issues and include
9+
"v5" in the title.
10+
11+
12+
## Standout improvements
13+
14+
- Commands are recognized without Verb-Noun format.
15+
16+
- Command arguments are more conscientiously marked,
17+
including unquoted strings.
18+
19+
- String contents are sometimes interpreted specially,
20+
though not in all cases. Some examples:
21+
22+
* Here-strings beginning with `using System` are
23+
highlighted with C#.
24+
25+
* Command argument strings recognize wildcards and
26+
path separators.
27+
28+
* Single-quoted strings in certain cases are
29+
highlighted with Regular Expressions.
30+
31+
* Other strings recognize some format placeholders.
32+
33+
- `using` imports can only come at the beginning of a file.
34+
35+
- `meta` scopes are used in more places, which doesn't
36+
typically affect highlighting, but sometimes has an
37+
effect on ST commands.

0 commit comments

Comments
 (0)