MobileNativeFoundation / MobileNativeFoundation/XCLogParser
Unused variable warning not being returned by the `parse` command
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 1.9k
- Forks
- 138
- PR merge metrics
- No merged PRs in 30d
Description
Description
Unused variable warning is not returned by the parse command when using --reporter issues.
Here is a sample app that I prepared: https://github.com/samuelsainz/unusedVariableSampleApp
This file is the xcactivitylog dumped with the dump command. You can see in this line that the warning is there.
Here you can see the output of the command:
xclogparser parse --file /Users/myuser/Library/Developer/Xcode/DerivedData/UnusedVariableWarningsSample-emoqxhjdjzmpatabnvgnsfcmgrkg/Logs/Build/BC2F776D-D644-46F6-AB7A-2CDBA1EF2073.xcactivitylog --reporter issues --output issues-output.json
XCLogParser version is 0.2.37
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported case with the linked xcactivitylog-dumped.json and the xclogparser parse --reporter issues command. Compare the warning near line 1070 with xclogparser-parse-report-issues.json and trace how that warning is handled by the issues reporter. Done means the unused-variable warning appears in the reporter output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100