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

The baseline use absolute path instead of relative file in the baseline content to identify a file #5599

Closed
2 tasks done
aiKrice opened this issue May 21, 2024 · 2 comments
Closed
2 tasks done
Labels
help Questions or user problems that require more explanation rather than code changes.

Comments

@aiKrice
Copy link

aiKrice commented May 21, 2024

New Issue Checklist

Describe the bug

The baseline.json use absolute path in the key: "file:" it should use relative path instead:

Complete output when running SwiftLint, including the stack trace and command used
$ swiftlint --write-baseline baseline.json --config .swiftlint.yml

Json piece:

...
,{
    "character" : 5,
    "file" : "\/Users\/christophersaez\/Documents\/projects\/shopmium-ios\/Packages\/Foundation\/Alamofire\/Sources\/Alam
ofire\/Request.swift",
    "line" : 255,
    "reason" : "All declarations should specify Access Control Level keywords explicitly",
    "rule_id" : "explicit_acl",
    "severity" : "Warning",
    "type" : "Explicit ACL"
  },
  ...

Environment

  • SwiftLint version (run swiftlint version to be sure)?
    0.55.1
  • Installation method used (Homebrew, CocoaPods, building from source, etc)?
    Homebrew
@aiKrice
Copy link
Author

aiKrice commented May 21, 2024

@mildm8nnered for info

@aiKrice
Copy link
Author

aiKrice commented May 21, 2024

Closed because baseline prettifier change the baseline format. Without that it's ok

@aiKrice aiKrice closed this as completed May 21, 2024
@SimplyDanny SimplyDanny added the help Questions or user problems that require more explanation rather than code changes. label Jun 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help Questions or user problems that require more explanation rather than code changes.
Projects
None yet
Development

No branches or pull requests

2 participants