actions / actions/toolkit

Problem Matchers: Higher scope for `message` property

Open
#1,471 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
5.9k
Forks
1.8k
PR merge metrics
No merged PRs in 30d

Description

Describe the enhancement
For the problem matchers, I have a special use case where an assertion in my code happens if some files are faulty. It would be pretty useful if I could match the message on the first pattern then loop through other lines to provide the files.

Maybe message property should be available in the pattern list but not necessarily for every object in pattern

Code Snippet

{
  "owner": "pytest",
  "pattern": [
    {
      "regexp": "^(FAILURE):\\s(.+)$",
      "message": 2
    },
    {
      "regexp": "^\\s+(.+)$",
      "file": 1,
      "loop": true
    }
  ]
}

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 with the problem matchers documentation linked in the issue and inspect the existing pattern schema and loop behavior. The issue names no implementation file or test; done should allow message on one pattern while subsequent lines provide files through looping.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 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.