GSoC 2026 India - DocC Language Features - First Contribution

Development GSoC
1

Hi @matthewbastien @snprajwal

I'm from India (Bengaluru), CS college student. Built FinanceAI SwiftUI app.

Super excited for DocC Language Features project!

Questions:

  1. Should I start with swift-syntax "good first issue"?
  2. VS Code setup for SourceKit-LSP?
  3. Priority: syntax highlighting or GoToDefinition?

Starting contributions TODAY!

2 Likes
2

Welcome to the Swift forums @Vansh!

I'd say the best places to start would be to familiarize yourself with:

Tackling some issues in SourceKit-LSP and the Swift extension would be a great way to familiarize yourself with the code. You'll want to get a development environment set up for both of these projects and maybe even the Swift DocC repo in case you need to make any changes there as well.

In my opinion, the Go To Definition and error reporting are far more important than syntax highlighting. Though of course it would be awesome if all of these could be accomplished within the project timeline!

Once you've got some form of initial proposal ready then it would be awesome if you posted it in the forums (either here or in a separate thread). I'd be happy to help guide you through fixing it up before the deadline. The earlier the better to give some time for feedback.

Good luck and don't hesitate to reach out with any other questions that you might have!

3

Thank you Matthew!

QUICK UPDATE: Just got my first PR merged in swiftlang/swift main (#87324 - computed property fix-its)!

Planning:

  1. 2-3 more swiftlang/swift diagnostics PRs
  2. THEN SourceKit-LSP DocC GoToDefinition (your priority)
  3. VSCode Swift extension

VSCode setup question: brew install sourcekit-lsp + vscode-swift extension?

Starting SourceKit-LSP clone tonight!

4

The SourceKit-LSP binary is available as part of the Swift toolchain which you can install from swift.org.

The Swift extension is available from the VS Code Marketplace or Open VSX. You can install it from within VS Code or one of its forks such as Cursor.

5

Hi @matthewbastien! Just a quick update. I've been exploring the SourceKit-LSP codebase and started working on issue #2256 (including DocC extension files in hover documentation). While diving in, I came across an interesting architectural challenge involving a circular module dependency between DocumentationLanguageService and SourceKitLSP. I've left a comment on the issue with my proposed solution would really appreciate your thoughts if you get a chance to take a look! Learning a lot from the codebase. Thank you!

6

Which of your PRs was successfully merged?

The issue you linked is still open and your PR is also still open: