Enhance language server spec

For https://github.com/krassowski/jupyterlab-lsp/pull/81#issuecomment-548042214

The current spec is a little limited as revealed in #81 for really driving UI. A more complete spec might be something like (not suggesting YAML, just easier to write):

# from spec version 0
argv: 
  - pyls
languages:
  - python
# definitely want
display_name: pyls
mime_types: # could be the source-of-truth instead of guessing in client
  - text/python
  - text/x-ipython
urls:
  home: https://github.com/palantir/python-language-server
  issues: https://github.com/palantir/python-language-server/issues
debug_argv: # will be complicated with helpers, e.g. r
  - pyls
  - v
# nice-to-have
config_schema: # it would be better to have these on the ts side, but...
  pyls.plugins.pydocstyle.enabled:
    type: boolean
    # so much more...
    # https://github.com/palantir/python-language-server/blob/develop/vscode-client/package.json
install: # for docs only
  pip: pip install python-language-server[all]
  conda: conda install -c conda-forge python-language-server
extend: # at least a few other servers are extensible
  - display_name: mypy 
    install: ...
  - display_name: isort
    install: ...
  - display_name: black
    install: ...
environment: # just because kernels have them
  PYTHONUNBUFFERED: "1"

This would necessitate a bump to the entry_point spec version, e.g. jupyter_lsp_spec_v1, though it may be possible to maintain backwards compatibility…

[bollwyvl]

It’s probably also worth generating some documentation from the schema: https://github.com/adobe/jsonschema2md

[bollwyvl]

I would imagine

/lsp/server/pyls

There’s no point to having the trailing python, as a single running server can handle multiple languages under the same process, to my understanding.

On Tue, Nov 5, 2019, 17:52 M. Krassowski [e-mail] wrote:

there’s no reason not to have one socket per language server, and it will advertise to the client what file extensions, mime types, etc. it supports. This would normalize a lot of things.

so we are heading towards /lsp/<server>/<language> as in /lsp/plys/python for the next spec version?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/krassowski/jupyterlab-lsp/issues/89?email_source=notifications&email_token=AAALCRGZLOSFM6MMTVOXAJ3QSH2JZA5CNFSM4JHVUCOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDET4WA#issuecomment-550059608, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAALCRALDINJZZMXN5CTLGLQSH2JZANCNFSM4JHVUCOA .