Looking at the PatternCompiler/PatternParser/PatternLexer trio, I fail to see where it can fail. They seem to be bullet-proof even with ill-written patterns. What would validate a ValidatingEntry then ?
Yeah that logic has changed a lot now and is more resilient to user errors (i.e. assumes more things are just text now). Probably needs some rethought, but there are too many use cases in the wild now for significant changes without breaking lots of people's set ups.
Anyway I found you can usually break it with # pretty easily - <#foo>
I recommend perhaps using a tied tag "<artist~title>" as it works better if is either is missing (e.g. in Classical music 0004. - - Sonata K.380.flac")
...unless those filenames themselves needs parsing by something strict I guess, but this is probably not the default case...
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.