Skip to content

Restore JetBrains integration and complete integration test coverage - #94

Merged
Lazarus-931 merged 1 commit into
mainfrom
fix/restore-jetbrains-coverage
Jul 24, 2026
Merged

Restore JetBrains integration and complete integration test coverage#94
Lazarus-931 merged 1 commit into
mainfrom
fix/restore-jetbrains-coverage

Conversation

@Lazarus-931

Copy link
Copy Markdown
Collaborator

While merging the approved integration PRs, I found that JetBrains (#90) never landed on main — its PR base was the stacked branch feat/integration-vscode, so the merge went there instead of main, and it diverged. This restores it and fixes the coverage test.

What

  • Restore JetBrains onto main: the jetbrains enum case, display/command/summary/install metadata, isGuidedSetup / guidedSetupSteps / guidedSetupCaveat, guided handling in the configure / configurationURL / launch switches, and its logo asset.
  • Complete coverage: add the four guided editors (VS Code, Cline, Cursor, JetBrains) to IntegrationServicesTests.coveredTools, so testEveryIntegrationHasCoverage (which asserts Set(IntegrationTool.allCases) == coveredTools) passes. They were omitted when the guided editors were introduced.

Checks

  • swiftc -parse on the changed Swift files.
  • coveredTools now equals all 16 IntegrationTool.allCases.

The JetBrains integration (PR #90) was merged into its stacked base branch
(feat/integration-vscode) rather than main, so it never landed. Re-add it
onto main: enum case, display/command/summary/install metadata, guided-setup
steps and caveat, guided handling in the service switches, and its logo.

Also add the guided editors (VS Code, Cline, Cursor, JetBrains) to the
coverage set so testEveryIntegrationHasCoverage matches every case in
IntegrationTool.allCases.
@Lazarus-931
Lazarus-931 merged commit b7bfe4a into main Jul 24, 2026
2 checks passed
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 this pull request may close these issues.

1 participant