LSP server settings has no effect

[igorechek06]

Relevance Confirmation

• I confirmed that this is not an issue with the Eclipse JDT Language Server itself

What happened?

I use this parameters in "lsp" section.

"jdtls": {
      "initialization_options": {
        "settings": {
          "java": {
            "inlayhints": {
              "parameterNames": {
                "enabled": "none"
              }
            }
          }
        }
      }
    }

But inlay hints continue to work.

What did you expect to happen?

I expected the settings to affect the LSP server

[igorechek06]

It just a little example. But I used settings from the example in README, and they still not work.

[igorechek06]

E.g. when I disable formatting, formatting still works.

[MarlinZapp]

I have the same problem. I first wanted to add a settings file that i have exported from eclipse as you can see below in the settings file. This had no effect, for example the lines do not break at 120.

{
  "languages": {
    "Java": {
      "formatter": "language_server"
    }
  },
  "lsp": {
    "jdtls": {
      "initialization_options": {
        "settings": {
          "java": {
            "jdt": {
              "ls": {
                "lombokSupport": {
                  "enabled": true
                }
              }
            },
            "format": {
              "settings": {
                "profile": "Line width 120",
                "url": "/path/to/my/formatter/file.xml"
              }
            }
          }
        }
      }
    }
  }
}

That's why i tried to do the format.enabled.false like @igorechek06 and the file still got formatted. It seems like the "language_server" formatter does not use the options given inside the jdtls initialization options.

[valentinegb]

Hey! Sorry, I've been sick for the last week, I'll finally fix this now ^^'

[MarlinZapp]

Hey, thanks for fixing! When do you plan to release a new version including this fix? So that we could test if it works for our cases?

[valentinegb]

Sorry about that, I was hoping I could get #43 resolved too but then I ended up not being able to do that. I’ll release a new version next time I get the chance today.