Simple danger-swift edit will succeed even if Dangerfile.swift has // fileImport: ~.
However, running on Xcode makes the working directory not to be the container of the Dangerfile.swift.
Though it can be resolved with --dangerfile option, it fails when the Dangerfile has // fileImport: ~.
$ danger-swift edit --dangerfile /path/to/danger/swift/Dangerfile.swift
ERROR: Error Domain=NSCocoaErrorDomain Code=260 "The file “ChangelogCheck.swift” couldn’t be opened because there is no such file." UserInfo={NSFilePath=DangerfileExtensions/ChangelogCheck.swift, NSUnderlyingError=0x7fcdb080a2f0 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"}}
I'm trying to resolve #563 and debugging on Xcode as above, this issue makes me a little inconvenience.
Simple
danger-swift editwill succeed even if Dangerfile.swift has// fileImport: ~. However, running on Xcode makes the working directory not to be the container of the Dangerfile.swift. Though it can be resolved with--dangerfileoption, it fails when the Dangerfile has// fileImport: ~.I'm trying to resolve #563 and debugging on Xcode as above, this issue makes me a little inconvenience.