virtual-code-owners 9.0.0 → 9.1.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +2 -3
- package/dist/version.js +1 -1
- package/dist/virtual-code-owners/parse.js +4 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -210,9 +210,8 @@ user/team names but doesn't verify their existence in the project.
|
|
|
210
210
|
(unless they're in a _section_ that has default owners `[sales related] @ch/sales`
|
|
211
211
|
in which case the rule inherits the default owners of that section)
|
|
212
212
|
- valid sections headings comply with the syntax described over at [GitLab](https://docs.gitlab.com/ee/user/project/codeowners/reference.html#sections)
|
|
213
|
-
>
|
|
214
|
-
> as a rule,
|
|
215
|
-
> to be the same as GitLab's in future releases without a major version bump.
|
|
213
|
+
> same as GitLab's syntax the line `[bla @group` is interpreted
|
|
214
|
+
> as a rule, and not as an erroneous section heading.
|
|
216
215
|
|
|
217
216
|
### Does virtual-code-owners support GitLab style sections?
|
|
218
217
|
|
package/dist/version.js
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
export const VERSION = "9.
|
|
1
|
+
export const VERSION = "9.1.0";
|
|
@@ -25,7 +25,10 @@ function parseLine(pUntreatedLine, pTeamMap, pLineNo) {
|
|
|
25
25
|
if (lTrimmedLine === "") {
|
|
26
26
|
return { type: "empty", line: pLineNo, raw: pUntreatedLine };
|
|
27
27
|
}
|
|
28
|
-
if (
|
|
28
|
+
if (
|
|
29
|
+
(lTrimmedLine.startsWith("[") || lTrimmedLine.startsWith("^[")) &&
|
|
30
|
+
lTrimmedLine.includes("]")
|
|
31
|
+
) {
|
|
29
32
|
return parseSection(pUntreatedLine, pLineNo, pTeamMap);
|
|
30
33
|
}
|
|
31
34
|
return parseRule(pUntreatedLine, pLineNo, pTeamMap);
|