MobileNativeFoundation / MobileNativeFoundation/XCLogParser
Populating `documentURL` for other `BuildStepType`s
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 1.9k
- Forks
- 138
- PR merge metrics
- No merged PRs in 30d
Description
I realize this is something that Apple is doing with their xcactivitylog. It appears with CompileC and CompileSwift that the documentURL will contain the file name of the file that is being compiled. This is populated by the DVTDocumentLocation.
It seems it would also be useful to have this information available to other compile types such as CompileStoryboard and CompileXIB. It does look like we should be able to derive this from the title.
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 tracing how documentURL is populated for CompileC and CompileSwift, then compare the BuildStepType handling for CompileStoryboard and CompileXIB. Use the title-derived filename as the proposed source, and consider the work done when those compile types expose the relevant file through documentURL consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100