Upgrade SwiftLint

[lawrence-forooghian]

To support Swift 6 syntax such as typed throws.

The changes are to address the violation of the optional_data_string_conversion rule.

Summary by CodeRabbit

• New Features

  • Updated SwiftLint dependency to improve code quality and linting capabilities.
  • Introduced a new Swift extension for the String class to enhance error handling during data decoding.

• Bug Fixes

  • Improved string handling in JSON serialization by ensuring UTF-8 encoding is explicitly specified.

[coderabbitai]

Walkthrough

The pull request introduces updates to the Mintfile and modifications to string handling in Swift files. The Mintfile reflects an upgrade of the SwiftLint dependency from version 0.55.1 to 0.57.0. In the Swift files, changes enhance string handling by replacing existing string decoding methods with a more explicit approach using String(data:encoding:). Additionally, a new Swift extension for String introduces a custom initializer that throws an error upon decoding failure, improving error handling in string operations.

Changes

File	Change Summary
Mintfile	Updated SwiftLint version from 0.55.1 to 0.57.0.
Sources/BuildTool/BuildTool.swift	Modified string handling in GenerateMatrices and Lint structs to use String(data:encoding:).
Sources/BuildTool/String+Decoding.swift	Added a new String extension with a custom initializer for decoding Data, throwing an error on failure.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant BuildTool
    participant StringExtension

    User->>BuildTool: Request string operation
    BuildTool->>StringExtension: Decode data to string
    StringExtension-->>BuildTool: Return decoded string or error
    BuildTool-->>User: Provide result

Loading

🐰 In the code garden, we hop and play,
With SwiftLint updated, we cheer today!
Strings now decode with care and grace,
Errors caught swiftly, no more a race.
Hopping through code, we make it bright,
A joyful journey, all feels just right! 🌟

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between cba40dc and 66ed42e.

Files selected for processing (3)

• Mintfile (1 hunks)
• Sources/BuildTool/BuildTool.swift (2 hunks)
• Sources/BuildTool/String+Decoding.swift (1 hunks)

Files skipped from review due to trivial changes (1)

• Mintfile

Files skipped from review as they are similar to previous changes (2)

• Sources/BuildTool/BuildTool.swift
• Sources/BuildTool/String+Decoding.swift

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  -- I pushed a fix in commit <commit_id>, please review it.
  -- Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  -- @coderabbitai generate unit testing code for this file.
  -- @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  -- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  -- @coderabbitai read src/utils.ts and generate unit testing code.
  -- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  -- @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.