You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can't use backslash ("") to escape characters in the regex provided to the scanning tool because they get converted to forward slashes ("/"), thereby invalidating the regex. For example:
/content/{re:"\[.*\]"}/
Results in:
[CommandError|120]: Command(166) has failed with: [ScanError|130]: [Errno 2] No such file or directory: '//content/{re:"/[.*/]"}'
The regex engine being used also seems to lack convenience tokens like /w and /W, and there doesn't seem to be a way to specify which part of the match should be taken as the collection/series/gallery token. For example, if I have:
The actual galleries are going to have the artist parsed as <artist> because it's in the name, but how do I get the series/grouping name to be <series> instead of [<artist>] <series>?
Environment:
OS: Ubuntu Server 22.04
Browser: Chrome 105.0.5195.54
HPX Version: 0.13.3 (client: 0.13.1)
Additional context
Installed via docker-compose.
The text was updated successfully, but these errors were encountered:
Can't use backslash ("") to escape characters in the regex provided to the scanning tool because they get converted to forward slashes ("/"), thereby invalidating the regex. For example:
Results in:
The regex engine being used also seems to lack convenience tokens like /w and /W, and there doesn't seem to be a way to specify which part of the match should be taken as the collection/series/gallery token. For example, if I have:
The actual galleries are going to have the artist parsed as
<artist>
because it's in the name, but how do I get the series/grouping name to be<series>
instead of[<artist>] <series>
?Environment:
Additional context
Installed via docker-compose.
The text was updated successfully, but these errors were encountered: