Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

error: ambiguous use of 'lint' #621

Closed
417-72KI opened this issue Sep 17, 2024 · 1 comment · Fixed by #622
Closed

error: ambiguous use of 'lint' #621

417-72KI opened this issue Sep 17, 2024 · 1 comment · Fixed by #622

Comments

@417-72KI
Copy link
Member

417-72KI commented Sep 17, 2024

/tmp/danger/CE34311C-313A-4804-B754-63A879562477/_tmp_dangerfile.swift:527:15: error: ambiguous use of 'lint'
    SwiftLint.lint(inline: true)
              ^
Danger.SwiftLint:13:24: note: found this candidate
    public static func lint(inline: Bool = false, directory: String? = nil, configFile: String? = nil, strict: Bool = false, quiet: Bool = true, lintAllFiles: Bool = false, swiftlintPath: String? = nil) -> [Danger.SwiftLintViolation]
                       ^
Danger.SwiftLint:18:24: note: found this candidate
    public static func lint(_ lintStyle: Danger.SwiftLint.LintStyle = .modifiedAndCreatedFiles(directory: nil), inline: Bool = false, configFile: String? = nil, strict: Bool = false, quiet: Bool = true, swiftlintPath: Danger.SwiftLint.SwiftlintPath? = nil, markdownAction: (String) -> Void = markdown) -> [Danger.SwiftLintViolation]
                       ^
�[31mERROR: Dangerfile eval failed at Dangerfile.swift
�[0;0m�[31mERROR: Could not get the results JSON file at /tmp/danger/CE34311C-313A-4804-B754-63A879562477/danger-response.json
�[0;0m

It seems to be caused by #610 and removing deprecated function ( lint(..., lintAllFiles:..) ) may be solve this 🤔

@npj008
Copy link

npj008 commented Sep 18, 2024

Facing same issue. Broken danger check pipeline. @f-meloni is there any way to install particular version of danger-swift using brew? 'tap/' is taking latest one only.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants