Pass `displayTypeErrors` as initialization options

[vanillajonathan]

Pyrefly v0.32.0 disabled type errors by default.

When I initialize the LSP by sending a initialize request I would like to be able to pass in the displayTypeErrors option in the initializationOptions property.

@SamChou19815

[SamChou19815]

It's unclear to me what you mean by this. This options will be sent by LSP compliant IDEs to the server if the option is in the config

[vanillajonathan]

In VS Code when I set the python.pyrefly.displayTypeErrors to force-on and activate verbose logging I see the "initialize" request which includes among the following:

    "initializationOptions": {
        "lspPath": "",
        "lspArguments": [
            "lsp"
        ],
        "trace": {
            "server": "verbose"
        }
    },

But displayTypeErrors is not mentioned in the initializationOptions. Later in response to workspace/configuration it sends:

        "pyrefly": {
            "disableLanguageServices": false,
            "displayTypeErrors": "force-on"
        },

I have written a client that use Pyrefly but my client does not have support for workspace, so I would like to be able to pass:

        "pyrefly": {
            "displayTypeErrors": "force-on"
        }

in the initializationOptions when my client sends the "initialize" request.

[SamChou19815]

@vanillajonathan

We do allow you to pass in arbitrary stuff to initializationOptions, we just ignore everything there.

It will be more helpful to describe what your client is. We are unlikely to maintain non-standard LSP behavior for non-IDE clients.

[vanillajonathan]

My client is a text editor where the text buffer is not persisted to disk, the code lives just in-memory, so I don't have any Python file, any workspace or any pyproject.toml or pyrefly.toml file.