Skip to content

Fix: Use Xcode diagnostic format patterns to avoid false positive error counts#4

Merged
drewster99 merged 1 commit intomainfrom
claude/issue-2-20260109-1949
Jan 9, 2026
Merged

Fix: Use Xcode diagnostic format patterns to avoid false positive error counts#4
drewster99 merged 1 commit intomainfrom
claude/issue-2-20260109-1949

Conversation

@drewster99
Copy link
Owner

Fixes #2

The previous regex patterns matched "error:" and "warning:" with word boundaries, which caused false positives from:

  • Objective-C method parameters like error:(NSError**)error
  • Code snippets in warning messages containing method signatures

Updated patterns now match only:

  • file:line:column: error: (typical compiler diagnostic format)
  • ^error: at start of line (standalone errors like linker errors)

This prevents false positives while catching all actual Xcode build errors.

Generated with Claude Code

…or counts

The previous regex patterns matched "error:" and "warning:" with word
boundaries, which caused false positives from:
- Objective-C method parameters like error:(NSError**)error
- Code snippets in warning messages containing method signatures

Updated patterns now match only:
- file:line:column: error: (typical compiler diagnostic format)
- ^error: at start of line (standalone errors like linker errors)

This prevents false positives while catching all actual Xcode build errors.

Fixes #2

Co-authored-by: Andrew Benson <drewster99@users.noreply.github.com>
@drewster99 drewster99 merged commit cf0f080 into main Jan 9, 2026
1 check passed
@drewster99 drewster99 deleted the claude/issue-2-20260109-1949 branch January 9, 2026 20:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bug: False positive error count due to regex matching "error:" in non-error contexts

1 participant

Comments