Add Wolfram Language support via official LSPServer paclet

[p135246]

Adds support for Wolfram Language (.wl, .wls files) using the official WolframResearch LSPServer paclet, which is bundled with Wolfram installations and communicates via stdio.

Requirements: Wolfram Mathematica 13.0+ or Wolfram Engine 12.1+. The WolframKernel executable is discovered via ls_path in ls_specific_settings.wolfram, the WOLFRAM_PATH environment variable, the system PATH, or common install locations. If no kernel is found, server startup fails with an actionable error message, and the test suite skips gracefully (using the same discovery logic).

Changes:

• WolframLanguageServer following the current DependencyProvider pattern (analogous to QML/MATLAB)
• WOLFRAM entry in LanguageServerId (file matcher for .wl/.wls, LS class factory)
• Test repo and test suite (document symbols incl. subdirectories, within-file references), wolfram pytest marker
• Docs: README language list, language support page, CHANGELOG

Known limitation: the LSPServer paclet computes textDocument/references per document — cross-file references are not supported by the server. This is noted in the docs and the test module.

Verified locally against Wolfram 14: integration tests pass (live LSP communication), and an end-to-end check through the MCP server (get_symbols_overview, find_symbol, find_referencing_symbols, get_diagnostics_for_file) works on a real Wolfram project. poe format, poe lint, and poe type-check are clean.

🤖 Generated with Claude Code

[opcode81]

@p135246 this is still a draft. Will you finalise this or shall we close it?

[p135246]

Hey @opcode81, I will give it a last vibecoding push now and let's see :-)

[Copilot]

Pull request overview

Adds first-class Wolfram Language (.wl, .wls) support to Serena/SolidLSP by integrating the official WolframResearch LSPServer paclet (via WolframKernel over stdio), plus corresponding tests, docs, and changelog updates.

Changes:

• Introduce WolframLanguageServer implementation with kernel discovery (PATH / WOLFRAM_PATH / common install locations) and stdio launch command.
• Register LanguageServerId.WOLFRAM with filename matching for .wl/.wls and LS class factory wiring.
• Add Wolfram integration test repo + pytest suite and surface Wolfram support in docs/README/CHANGELOG.

Reviewed changes

Copilot reviewed 10 out of 11 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
src/solidlsp/language_servers/wolfram_language_server.py	New Wolfram Language server integration and kernel discovery/launch logic.
src/solidlsp/ls_config.py	Adds LanguageServerId.WOLFRAM, file matcher for .wl/.wls, and LS class mapping.
test/conftest.py	Adds Wolfram gating logic to disable tests when WolframKernel is unavailable.
test/solidlsp/wolfram/test_wolfram_basic.py	Adds basic Wolfram symbols + within-file and cross-file references tests.
test/solidlsp/wolfram/__init__.py	Initializes Wolfram test package.
test/resources/repos/wolfram/test_repo/main.wl	Wolfram fixture repo main file for symbols/references tests.
test/resources/repos/wolfram/test_repo/lib/helper.wl	Wolfram fixture helper file for cross-file references tests.
pyproject.toml	Adds wolfram pytest marker.
README.md	Adds Wolfram Language to supported language list.
docs/01-about/020_programming-languages.md	Documents Wolfram Language support and prerequisites.
CHANGELOG.md	Notes Wolfram Language support and requirements.

[p135246]

Addressed the Copilot review in the latest push:

1. conftest skip logic — now reuses the language server's own _find_wolfram_kernel() discovery helper instead of duplicating a subset of the search paths, so test gating matches runtime behavior (including WOLFRAM_PATH and Linux/Windows locations).
2. Within-file references test — the assertion now requires both the definition site and the call site, matching the comment.
3. Cross-file references test — removed. Verified against a live kernel that the LSPServer paclet computes textDocument/references per document only (cross-file references are not supported by the server), so the test could never validate what its name claimed. The limitation is now noted in the test module, the docs page, and the CHANGELOG entry.

🤖 Generated with Claude Code

[Copilot]

Pull request overview

Copilot reviewed 10 out of 11 changed files in this pull request and generated 2 comments.

Comments suppressed due to low confidence (1)

test/conftest.py:485

• The Wolfram test enablement check only looks at PATH + macOS .app locations, so tests will be incorrectly skipped on Linux/Windows when WolframKernel is installed in a common location but not on PATH. This diverges from the actual server discovery logic and can hide regressions on those platforms.

    # Disable Wolfram tests if WolframKernel is not available (checked with the same
    # discovery logic used by the language server itself)
    from solidlsp.language_servers.wolfram_language_server import _find_wolfram_kernel

    try:

[p135246]

Addressed the second review round:

1. "semantic highlighting" in CHANGELOG — removed; the initialize params indeed do not advertise semanticTokens.
2. Explicit negative test — added test_wolfram_no_cross_file_references, asserting that references for a symbol defined in lib/helper.wl and called in main.wl stay within lib/helper.wl. If a future LSPServer version adds cross-file support, this test will fail and prompt a documentation update. The PR description was already updated to state within-file-only references.

🤖 Generated with Claude Code

[Copilot]

Pull request overview

Copilot reviewed 10 out of 11 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (1)

CHANGELOG.md:20

• CHANGELOG claims Wolfram Language support includes “semantic highlighting”, but the WolframLanguageServer client capabilities added in this PR don’t advertise any semanticTokens support (see WolframLanguageServer._create_base_initialize_params), so this feature claim appears unsupported/inaccurate.

    within-file references, hover documentation, and formatting.

[Copilot]

Pull request overview

Copilot reviewed 10 out of 11 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (1)

test/solidlsp/wolfram/test_wolfram_basic.py:50

• SolidLanguageServer.request_references() sends textDocument/references with includeDeclaration: False (see solidlsp/ls.py), so the definition site is not guaranteed to be returned. This test currently requires the definition line (2) to be present, which will fail on servers that follow the spec strictly.

        assert ("main.wl", 2) in reference_lines, f"Expected the definition site among references, got {reference_lines}"
        assert ("main.wl", 10) in reference_lines, f"Expected the call site among references, got {reference_lines}"

[p135246]

[Copilot]

Pull request overview

Copilot reviewed 11 out of 12 changed files in this pull request and generated 2 comments.

Comments suppressed due to low confidence (1)

test/solidlsp/wolfram/test_wolfram_basic.py:50

• SolidLanguageServer.request_references() sends includeDeclaration=False (see src/solidlsp/ls.py:1622-1628), so the declaration/definition location should not be asserted as part of the references list here. This test will be brittle (and likely fail) if the server respects includeDeclaration.

Adjust the assertion to only require the non-declaration call site reference.

        # 'calculateSum' is defined on line 2 of main.wl and called on line 10 (0-based)
        references = language_server.request_references("main.wl", line=2, column=0)

        reference_lines = {(ref["relativePath"], ref["range"]["start"]["line"]) for ref in references}
        assert ("main.wl", 2) in reference_lines, f"Expected the definition site among references, got {reference_lines}"
        assert ("main.wl", 10) in reference_lines, f"Expected the call site among references, got {reference_lines}"

[Copilot]

Pull request overview

Copilot reviewed 11 out of 12 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (3)

test/solidlsp/wolfram/test_wolfram_basic.py:50

• This test assumes the reference results include the declaration/definition site, but SolidLanguageServer.request_references() sends includeDeclaration=False (see src/solidlsp/ls.py), so depending on server behavior this assertion can be wrong/flaky. Prefer asserting only non-declaration usages (e.g. query from the call site and assert the call site is returned).

        references = language_server.request_references("main.wl", line=2, column=0)

        reference_lines = {(ref["relativePath"], ref["range"]["start"]["line"]) for ref in references}
        assert ("main.wl", 2) in reference_lines, f"Expected the definition site among references, got {reference_lines}"
        assert ("main.wl", 10) in reference_lines, f"Expected the call site among references, got {reference_lines}"

src/solidlsp/ls_config.py:191

• The WOLFRAM enum docstring says to configure ls_path in ls_specific_settings, but elsewhere (and in the error message) the key is ls_specific_settings.wolfram. Aligning this avoids confusing users configuring Wolfram.

    Set WOLFRAM_PATH environment variable or configure ls_path in ls_specific_settings.

test/conftest.py:484

• This check uses _find_wolfram_kernel() which currently considers WOLFRAM_PATH, PATH, and common install locations, but not ls_specific_settings.wolfram.ls_path. The comment claiming it uses “the same discovery logic used by the language server itself” is therefore slightly inaccurate; clarify the comment to match what’s actually checked.

    # Disable Wolfram tests if WolframKernel is not available (checked with the same
    # discovery logic used by the language server itself)
    from solidlsp.language_servers.wolfram_language_server import _find_wolfram_kernel

[p135246]

Shall we merge or close @opcode81? The Wolfram LSP is not that strong yet (no crossfile references), but I've been using it anyway...

[AmirF194]

is_ignored_dirname (src/solidlsp/language_servers/wolfram_language_server.py:53-59) matches Documentation and FrontEnd against any path component, not just the Wolfram installation layout. Verified on this PR's HEAD (41894ec):

obj = object.__new__(WolframLanguageServer)
obj.is_ignored_dirname("Documentation")  # True
obj.is_ignored_dirname("FrontEnd")       # True

should_ignore_path in ls.py checks every directory component of a file's path against this, so a .wl file under a user's own Documentation/ or FrontEnd/ folder (both plausible project directory names, unlike the Mathematica-specific .Wolfram/SystemFiles) would be silently skipped from indexing, with no error.

Every other is_ignored_dirname override in this codebase (csharp: bin/obj/packages, elm: elm-stuff, haskell: dist-newstyle, etc.) sticks to build-tool or vendor-specific names that are unlikely to collide with a user's own source tree. Would it work to scope this to the actual bundled-app locations instead (for example checking that the matched dir sits under the resolved kernel's installation path), or drop Documentation/FrontEnd if they were only meant as a defensive guess?

[MischaPanch]

Thanks for the input @AmirF194 . Yes, these are very generic directory names - do they have some fixed meaning in wolfram projects? If they usually do carry mathematica files, why would you want to exclude them from indexing? And if they don't carry mathematica files, there's no need to exclude them

@p135246 we can merge this after the ignored dir names issue is resolved, some wolfram support is better than no wolfram support at all.

[opcode81]

Thanks for your contribution