You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: packages/annotation-comments/CHANGELOG.md
+33Lines changed: 33 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,38 @@
1
1
# annotation-comments
2
2
3
+
## 1.0.0
4
+
5
+
### Major Changes
6
+
7
+
- a5b2179: First major release. Mainly to ensure that semver ranges work as expected, but hooray! 🎉
8
+
9
+
### Minor Changes
10
+
11
+
- a5b2179: Adds support for target ranges defined by matching `start`...`end` annotation comments. This allows you to annotate ranges of code without having to count lines or manually updating the ranges when the code changes.
12
+
13
+
The following example shows how to define a simple target line range using the new feature:
14
+
15
+
```js
16
+
// [!mark:start]
17
+
functionfoo() {
18
+
console.log('foo')
19
+
}
20
+
// [!mark:end]
21
+
```
22
+
23
+
You can also combine `start`...`end` ranges with search queries, which limits the search to the range defined by the `start` and `end` annotation comments:
24
+
25
+
```js
26
+
// [!mark:"log":start]
27
+
functionfoo() {
28
+
console.log('The words "log" will be marked both in the method call and this text.')
29
+
console.log('Also on this line.')
30
+
}
31
+
// [!mark:"log":end]
32
+
33
+
console.log('As this line is outside the range, "log" will not be marked.')
0 commit comments