-
Notifications
You must be signed in to change notification settings - Fork 37
Support capture groups in template #33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Another option instead of supporting capture groups is to give simple const primitives to us, such as:
then rule becomes:
then header can support (when year ends):
|
Hi @just-at-uber , I have extended the plugin to support an requeriment of mine, which is similar to yours. If the PR #53 gets merged, you can use the newly added option to fulfill your requirment too. Cheers! |
Hi. Just FYI, @just-at-uber has left Uber and isn't responding to emails anymore. This is the OSPO, where things got redirected. |
Hi @jonathanbaker7, Noted. Thanks for informing. :) |
Uh oh!
There was an error while loading. Please reload this page.
Right now this library can detect if a given header is in violation of the rules specified in a pattern. If the pattern is partially matched, it would be nice to be able to reference capture groups in the pattern and apply those capture groups into the template (if matched), otherwise leave blank.
For example:
Say my header & configuration looked like the following:
Actual behavior
header:
rule:
and time ticked over to 2021
header (fixed):
Desired behavior
header:
rule:
When the year ticks over to 2021, it would be nice if it updated current year only, and left first year as-is.
header (fixed):
The text was updated successfully, but these errors were encountered: