guard / guard/guard

feature request: Make watch() matches behave like a regexp results

Open
#797 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

✨ Feature
Dominant language
Ruby
Stars
6.4k
Forks
493
PR merge metrics
No merged PRs in 30d

Description

Currently, the watch() block passes an array, not a regexp result, e.g.:

watch(/f(oo)/) { |m| "#{m[1]}" }

works, but the following doesn't:

watch(/f(?<name>oo)/) { |m| "#{m[:name]}" }

Reason: guard template rules could become more readable and robust

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the Ruby implementation of watch() and how regexp matches are passed into the block; no specific file or test is named in the issue. Done means named captures such as m[:name] work while the existing positional capture behavior remains supported.

Written by the indexing model from the issue text.

Assessment

Tech stack
ruby
Domain
cli
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.