feat: add setting for showing linting fixes

[Hellebore]

Checklist

• If package.json or yarn.lock have changed, then test the VSIX built by yarn run vsce package works from a direct install

Summary by Sourcery

New Features:

• Add a user setting to show linting fixes for all problems.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request introduces a new setting to control the display of linting fixes, and passes this setting to the language server.

Sequence diagram for language server initialization with new linting setting

sequenceDiagram
    participant Extension
    participant Workspace
    participant LanguageClient
    Extension->>Workspace: getConfiguration('sourcery')
    Workspace-->>Extension: configuration
    Extension->>Extension: get<boolean>('lintingFixes')
    Extension->>LanguageClient: initialize with show_linting_fixes
    Note right of LanguageClient: New setting passed to server

Loading

Class diagram showing updated configuration settings

classDiagram
    class SourceryConfiguration {
        +boolean codeLens
        +boolean lintingFixes
        +boolean ruleType.refactorings
    }
    note for SourceryConfiguration "New lintingFixes setting added"

Loading

File-Level Changes

Change	Details	Files
Added a new setting to control the display of linting fixes.	Added the sourcery.lintingFixes setting to the package.json file with a default value of true and a description of 'Show linting fixes for all problems.'	package.json
Pass the new setting to the language server.	Read the sourcery.lintingFixes setting from the workspace configuration. Pass the show_linting_fixes setting to the language server during initialization	src/extension.ts

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @Hellebore - I've reviewed your changes - here's some feedback:

Overall Comments:

• Please verify and check off the PR checklist item about testing the VSIX package installation, since package.json was modified.

Here's what I looked at during the review

• 🟢 Functionality: all looks good
• 🟡 General issues: 1 issue found
• 🟢 Security: all looks good
• 🟢 Review instructions: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

LangSmith trace

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}