You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 35aba4e
Browse filesBrowse the repository at this point in the historyBrowse files
code-lsp: a package for each purpose, exported as a module
The module does several things, each now in a package of its own:
- org.scijava.code.lsp: brokering between scripts and servers (the
service, plugins, script sessions, environments), plus SciJava's
additions to LSP (updating completion lists, rated signatures).
- .launch: running language server processes.
- .script: SciJava scripts as plain code (#@ parameters declared).
- .jvm: a toolkit for in-process servers of JVM languages.
- .impl: the implementation, not exported.
The specialized packages depend only on the base package, never on
each other. A module-info exports the four public packages; it is open,
for SciJava Common's reflection. Package infos say what each is for.
To keep the implementation internal, clients get sessions via
ScriptSession.owning, the service no longer offers its servers directly
(LanguageServerService.server), and data is no longer assumed to be
Gson's (the module no longer reads Gson).
Tests run on the classpath, not the module path, where the tests'
plugin index would shadow the module's own.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
0 commit comments