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
and then add it's compatriot for consistency as an alias to the current behavior
example.txt##user.EQ.root
of course this could create one problem, what if you have a pattern that has a dot in it, in that case I'd guess you'd have to do 2 things, one maybe make this a toggle feature for now, and if they do toggle it, they have to use the operator if its going to be ambiguous, or they just have to do that period. You could consider then in a next major version whether to deprecate/remove the old behavior.
Describe alternatives you've considered
obviously you can use the if/else/include pattern with a template, but that's kind of cludgy if you want the whole file
The text was updated successfully, but these errors were encountered:
This issue has been labeled as stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.
This issue has been labeled as stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.
Is your feature request related to a problem? Please describe.
I'd like to be able to negate a alternate match in the filename
Describe the solution you'd like
I think something like (and I can't believe I'm suggesting the fortran operator, but for shell safety... unless you want to parse unicode https://en.wikipedia.org/wiki/Relational_operator)
and then add it's compatriot for consistency as an alias to the current behavior
of course this could create one problem, what if you have a pattern that has a dot in it, in that case I'd guess you'd have to do 2 things, one maybe make this a toggle feature for now, and if they do toggle it, they have to use the operator if its going to be ambiguous, or they just have to do that period. You could consider then in a next major version whether to deprecate/remove the old behavior.
Describe alternatives you've considered
obviously you can use the if/else/include pattern with a template, but that's kind of cludgy if you want the whole file
The text was updated successfully, but these errors were encountered: