Description
Is your feature request related to a problem? Please describe.
When working with varied log formats, I've supplied multiple regex patterns to parse them. However, due to development and debugging scenarios, there are always edge cases that don't match any pattern. When the cursor is positioned on these unmatched logs, an additional line appears: "Invalid log message: Log line does not match any pattern". This warning significantly impacts my user experience by adding visual noise.
I attempted to resolve this by adding a catch-all pattern (^(?<timestamp>)(?<body>.*)$), but this overly generic regex causes all my specific patterns to be bypassed, as everything matches this generic pattern first.
Describe the solution you'd like
I'd like an option to suppress the "Invalid log message" warnings. This could be implemented as:
- A configuration flag like
suppressInvalidLogWarnings: true/false - An option in the settings UI to toggle these warnings
- A way to mark certain patterns as "fallback" patterns that don't trigger warnings
Describe alternatives you've considered
- Using a catch-all regex pattern, but as mentioned, this nullifies all my specific patterns
- Ignoring the warnings, but they're quite distracting during development
- Trying to create extremely comprehensive regex patterns, which is time-consuming and still prone to miss edge cases
Additional context
This issue is particularly important in development environments where log formats might be in flux or experimental formats are being used. The ability to suppress these warnings would make the tool more flexible for various workflows without sacrificing its core functionality.