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
Is your feature request related to a problem? Please describe.
Currently, when making capture groups, we can only access $Matches.Groups[uint].Value, sometimes you may need to access the actual Captures in each group, for example.
(foo){2}(bar)
So how do we access the foos? We can't. $Matches.Groups[1].Value is foofoo, and $Matches.Groups[2].Value is bar. We need $Matches.Groups[1].Captures[0] & $Matches.Groups[1].Captures[1]. The only thing you can actually do at the moment's copy-paste the regex again, and add named groups, that's not good.
Describe the solution you'd like
So this is the tough part. We'd want to use a character delimiter that can't appear in URIs to delimit the variable in the autoupdate.url, so maybe something like $match1\capture1 or $match1$capture1.
The text was updated successfully, but these errors were encountered:
brian6932
changed the title
[Feature] A way to access $Matches.Groups[uint].Captures[uint]
[Feature] A way to access $Matches.Groups[uint].Captures[uint] within autoupdateApr 19, 2024
Feature Request
Is your feature request related to a problem? Please describe.
Currently, when making capture groups, we can only access
$Matches.Groups[uint].Value
, sometimes you may need to access the actualCaptures
in each group, for example.So how do we access the
foo
s? We can't.$Matches.Groups[1].Value
isfoofoo
, and$Matches.Groups[2].Value
isbar
. We need$Matches.Groups[1].Captures[0]
&$Matches.Groups[1].Captures[1]
. The only thing you can actually do at the moment's copy-paste the regex again, and add named groups, that's not good.Describe the solution you'd like
So this is the tough part. We'd want to use a character delimiter that can't appear in URIs to delimit the variable in the
autoupdate.url
, so maybe something like$match1\capture1
or$match1$capture1
.The text was updated successfully, but these errors were encountered: