Releases: MobileNativeFoundation/XCLogParser
Releases · MobileNativeFoundation/XCLogParser
Treat warnings as errors if the build was configured like that
- If the build is treating clang warnings as errors, the parse command will report them as errors
- Add new type of errors: linker errors and build phase's scripts errors
More issues categories and better Swift issues details
- Fixes a bug where line and column numbers were reported by a one-off error
- Categorizes more types of issues, such as
.deprecatedWarningandLexicalerrors - Details about Swift errors and warnings are attributed to the right issue.
Bug fixing
Fixes a bug in the parser: if a File contained both warnings and errors, only the warnings were being reported.
Errors details
- The
parsecommand shows more detail about the errors found in the logs - Fixes a bug where the Swift errors were not shown when the app was compiled with
whole-module
Issues reporter
- Fixes a bug where the Clang errores were not reported for Xcode 11.4
- Adds a new reporter to the
parsecommand that outputs only the errors and warning found in the Build log.
Swiftc type checker times and HTML report revamped
- The
parsecommand parses the Swiftc check type times if the project was compiled with the options-Xfrontend -debug-time-expression-type-checking. - The HTML report shows only the targets and files that were actually compiled, to mimic the behaviour of Xcode's build report.
- The HTML report displays a table with the Swiftc build times.
Bug fixing
- Fixes a bug that produced an empty compilationEndDate when a target didn't compile a single file
Versioning update
Merge pull request #68 from spotify/20200228-bump-version Bump version to 0.2.7
Strict project name parameter
Bug fixing
Fixes these bugs:
- Compilation duration wasn't discarding steps fetched from cache
- When parsing builds with Whole module enabled, duplicated identifiers were being generated for Swift steps
