actions / actions/toolkit

Problem Matchers: missing `endLine` and `endColumn` fields

Open
#907 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Describe the bug
The endLine and endColumn properties are supported by the AnnotationProperties type as of f0b00fd201c7ddf14e1572a10d5fb4577c4bd6a2, but missing from Problem Matchers.

In the same fashion, line and column fields are utilizing old naming and should probably be called startLine and startColumn, respectively.

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

Open docs/problem-matchers.md and compare its single-line matcher fields with AnnotationProperties in packages/core/src/core.ts. Update the documentation so the supported endLine/endColumn fields and startLine/startColumn naming are represented, then verify the field descriptions use the same names.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.