Fix readme and add options documentation

[igorechek06]

I just stole the documentation.

[valentinegb]

I'm not sure if this is a good idea. JDTLS updates independently of the extension and if we keep documentation on JDTLS it can very easily become out-of-date and inaccurate. Also, users of the extension can use whatever version of JDTLS they want, so we should leave it up to them to find the documentation for the right version.

[appelgriebsch]

this is rather 4 I guess?!

[igorechek06]

Sorry, it's my typo

[valentinegb]

I'm not sure if this is a good idea. JDTLS updates independently of the extension and if we keep documentation on JDTLS it can very easily become out-of-date and inaccurate. Also, users of the extension can use whatever version of JDTLS they want, so we should leave it up to them to find the documentation for the right version.

I'm open to being convinced that I'm wrong, hence why I've left the issue open thus far, but if my concerns aren't addressed I'm going to close this without merging eventually.

[lukejans]

Hi everyone,

Thanks for opening this discussion! I’ve been trying to clarify exactly which features the zed-java extension supports, but haven’t found much documentation yet. Since I installed it, I’ve been experimenting with code actions and I’m not sure if they’re actually supported or if I’ve misconfigured something.

Here’s what I’m trying to use to enable the qualifyMembers and qualifyStaticMembers cleanup actions:

{
  "jdtls": {
    "initialization_options": {
      "settings": {
        "java": {
          "cleanup": {
            "actions": ["qualifyMembers", "qualifyStaticMembers"],
            "actionsOnSave": ["qualifyMembers", "qualifyStaticMembers"]
          }
        }
      }
    }
  }
}

I based this on the Red Hat vscode‑java extension and the eclipse.jdt.ls initialization guide, but I haven’t seen any effect in Zed. Could someone confirm whether code actions (like cleanup) are supported by zed-java? If they’re not yet implemented, any pointers on where to find documentation—or proposals for adding some to avoid this problem—would be hugely appreciated.

Thanks for your help!