oxlint/oxfmt LSPs do not initialize on startup for previously opened files

[hanneswidrig]

I followed the default example but I'm facing issues with the oxlint and oxfmt LSPs actually running initially when I launch zed.

Reproduction Steps

1. Open a basic typescript project with zed settings configuration globally or locally.
2. Open a typescript file.
3. Close the editor and relaunch.
4. Observe that oxlint and oxfmt are not recognized in that typescript file.

5. Close and reopen a typescript file, now oxlint and oxfmt are running and active.

// .zed/settings.json
{
  "lsp": {
    "oxlint": {
      "initialization_options": {
        "settings": {
          "configPath": null,
          "run": "onType",
          "disableNestedConfig": false,
          "fixKind": "safe_fix",
          "typeAware": true,
          "unusedDisableDirectives": "deny"
        }
      }
    },
    "oxfmt": {
      "initialization_options": {
        "settings": {
          "fmt.configPath": null,
          "run": "onSave"
        }
      }
    }
  },
  "languages": {
    "TypeScript": {
      "format_on_save": "on",
      "prettier": {
        "allowed": false
      },
      "formatter": [
        {
          "language_server": {
            "name": "oxfmt"
          }
        }
      ]
    }
  }
}

[chungweileong94]

Pretty sure this is not extension issue, but a bug from Zed
zed-industries/zed#40193
zed-industries/zed#47054

[dnery]

Yeah it's 100% on Zed's side... I've been pulling my hair for the last couple of hours trying to understand why the LSP didn't seem to work on files that were already opened (TOML, JSON, JSONC, TypeScript, few others).

It's the most unique editor out there while at the same time being the most unreliable, somehow. This coupled with the fact that I'll just randomly find it using 14GB of RAM helped me develop a tempestuous love-hate relationship with it.

[chungweileong94]

This has been fixed upstream zed-industries/zed#51308.