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
In my experience, it's pretty common for some patterns. especially metavariable-pattern, to be repeated in lots of rules to refine matches or define classes of passing / failing constructs.
It would be nice to have an easy way to define patterns possibly independent from rules, and then invoke them from rules instead of having to copy/paste the same patterns over and over.
This is somewhat related to #3758: expressing non-literal strings is a bit verbose and somewhat error prone because of yaml, the ability to define reusable metavariable patterns would allow defining a single "non-literal" pattern, and then invoke that every time we want to make that assertion.
The text was updated successfully, but these errors were encountered:
In my experience, it's pretty common for some patterns. especially
metavariable-pattern
, to be repeated in lots of rules to refine matches or define classes of passing / failing constructs.It would be nice to have an easy way to define patterns possibly independent from rules, and then invoke them from rules instead of having to copy/paste the same patterns over and over.
This is somewhat related to #3758: expressing non-literal strings is a bit verbose and somewhat error prone because of yaml, the ability to define reusable metavariable patterns would allow defining a single "non-literal" pattern, and then invoke that every time we want to make that assertion.
The text was updated successfully, but these errors were encountered: