I've been reproducing more error types in Xcode and then try to parse them with XCLogParser. This PRs adds those that weren't categorised as Errors or Warnings.
I also just noted that the line and column numbers that Xcode reports are zero-based, so I'm adding 1 to them to have an accurate number.
I'm introducing a new kind of warning: deprecatedWarning to mark Clang and Swiftc deprecation issues. Handy if you want to track deprecations in your project and inform the users about them.
Finally, there was a long standing bug: Swiftc reports the error/warning details of a file in a single String. I'm parsing that large string and attribute each detail to the right error/warning.
I've been reproducing more error types in Xcode and then try to parse them with XCLogParser. This PRs adds those that weren't categorised as Errors or Warnings.
I also just noted that the line and column numbers that Xcode reports are zero-based, so I'm adding 1 to them to have an accurate number.
I'm introducing a new kind of warning:
deprecatedWarningto mark Clang and Swiftc deprecation issues. Handy if you want to track deprecations in your project and inform the users about them.Finally, there was a long standing bug: Swiftc reports the error/warning details of a file in a single String. I'm parsing that large string and attribute each detail to the right error/warning.
cc @alrocha @BalestraPatrick @polac24