refactor(swiftlint): remove blanket_disable_command from disabled rules

[jon-tous]

There are no violations currently in the project. We can enable this rule moving forward to prevent future violations.

Contributor checklist

• This pull request is on a separate branch and not the main branch

---

Description

I removed blanket_disable_command from disabled_rules in .swiftlint.yml and no violations were flagged.

Running swiftlint --strict confirmed: Done linting! Found 0 violations, 0 serious in 86 files. This rule can now be enforced by SwiftLint moving forward to prevent new violations from entering the codebase.

The only change was removing this line from from .swiftlint.yml so no functionality is affected. App builds and runs as normal on iPhone 15 Pro simulator (iOS 17.5).

Related issue

• SwiftLint: Fix blanket_disable_command throughout codebase #427

[github-actions]

Thank you for the pull request!

The Scribe team will do our best to address your contribution as soon as we can. The following is a checklist for maintainers to make sure this process goes as well as possible. Feel free to address the points below yourself in further commits if you realize that actions are needed :)

If you're not already a member of our public Matrix community, please consider joining! We'd suggest using Element as your Matrix client, and definitely join the General and iOS rooms once you're in. Also consider joining our bi-weekly Saturday dev syncs. It'd be great to have you!

Maintainer checklist

• The commit messages for the remote branch should be checked to make sure the contributor's email is set up correctly so that they receive credit for their contribution

  • The contributor's name and icon in remote commits should be the same as what appears in the PR
  • If there's a mismatch, the contributor needs to make sure that the email they use for GitHub matches what they have for git config user.email in their local Scribe-iOS repo

• The linting and formatting workflows within the PR checks do not indicate new errors in the files changed

• The CHANGELOG has been updated with a description of the changes for the upcoming release and the corresponding issue (if necessary)

[andrewtavis]

Thanks, @jon-tous! Maybe the earlier issues were fixed as we worked on other issues 😊