提交 85b001da 编写于 作者: D Dirk Baeumer

Fixes #8562: Problem matcher should use unique onwer if omitted

上级 35204a12
......@@ -11,6 +11,7 @@ import * as Strings from 'vs/base/common/strings';
import * as Assert from 'vs/base/common/assert';
import * as Paths from 'vs/base/common/paths';
import * as Types from 'vs/base/common/types';
import * as UUID from 'vs/base/common/uuid';
import Severity from 'vs/base/common/severity';
import URI from 'vs/base/common/uri';
......@@ -664,7 +665,7 @@ export namespace Config {
* The owner of the produced VSCode problem. This is typically
* the identifier of a VSCode language service if the problems are
* to be merged with the one produced by the language service
* or 'external'. Defaults to 'external' if omitted.
* or a generated internal id. Defaults to the generated internal id.
*/
owner?: string;
......@@ -772,7 +773,7 @@ export class ProblemMatcherParser extends Parser {
private createProblemMatcher(description: Config.ProblemMatcher): ProblemMatcher {
let result: ProblemMatcher = null;
let owner = description.owner ? description.owner : 'external';
let owner = description.owner ? description.owner : UUID.generateUuid();
let applyTo = Types.isString(description.applyTo) ? ApplyToKind.fromString(description.applyTo) : ApplyToKind.allDocuments;
if (!applyTo) {
applyTo = ApplyToKind.allDocuments;
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册