Problem matcher multiline support for message field

[stefanbuck]

Describe the enhancement

It seems like the current implementation does not support escape sequences like \n or \t for the message field. I wonder if there is a special reason for that. I want to write a Problem Matcher for jest and this requires multiline support to make the output useful.

Current dialog

Expected dialog

[JasonGross]

There's some documentation here on how to match multiline error messages by giving separate regexps for each line, and optionally looping the final regexp until no match is found. Is this sufficient, or do you need more flexibility?

[stefanbuck]

The issue describes a limitation on the message field and the way how it is present in the UI. It doesn't support multiple lines which is needed to provide useful jest output to the user.

[stefanbuck]

URL encoding \n does the trick.

[mattmurp]

@stefanbuck can you provide an example of how you achieved this? When I use the following:
annotationString = annotationString.replace(/\r?\n/g, "%0A");
My annotation appears as a really long single line string with %0A in place of the newlines.
For example:
Expected Result:

 This
 Is
 Multiline
 Annotation

Actual Result:

 This%0AIs%0AMultiline%0AAnnotation

[stefanbuck]

Sure, here it is https://github.com/stefanbuck/jest-matcher/pull/2/files#diff-25e722d9e112f063d137dc80dd8f9664R18

[mattmurp]

Thanks, that worked!

[teohhanhui]

The workaround by @stefanbuck basically doesn't use problem matchers.

So this is still a desirable feature, to be able to match a single error which spans multiple lines of output.