Workspace config init/updating doesn't work for Doom Emacs

[BeBel42]

Hi, I am trying to setup odoo-lsp in doom emacs.

While I already managed to setup other LSPs, I have an issue with odoo-lsp. Here is what I get:

ERROR odoo_lsp::server src/server.rs Could not parse updated configuration for /home/odoo/odoo/community:
invalid type: null, expected struct Config
ERROR odoo_lsp::server src/server.rs Could not parse updated configuration for /home/odoo/odoo/enterprise:
invalid type: null, expected struct Config

I have tried to check the cause of the error myself (and read server.rs). But I can't understand what causes the issue.

/home/odoo/odoo/community and /home/odoo/odoo/enterprise are both correct paths. Here is my .odoo_lsp file, located in /home/odoo/odoo:

{
  "module": {
    "roots": [
      "./community",
      "./enterprise"
    ]
  },
  "symbols": {
    "limit": 80
  },
  "references": {
    "limit": 80
  },
  "completions": {
    "limit": 200
  }
}

I am on the latest nightly version (updated today).

Have you got any idea of what could cause the error?

[Desdaemon]

Hi, thanks for your interest in odoo-lsp!

The configuration updating is a bit half-baked, but they read from your editor LSP configuration instead of the .odoo_lsp files for now. In any case it should not affect the first boot of the server, but I'm not knowledgeable in how Emacs manages workspaces and LSP servers so I might be wrong.

[BeBel42]

When I change my .odoo_lsp file, the error message's path changes accordingly. So it looks like it is reading it..? When I pass my root paths manually to the odoo-lsp executable, the same issues arises...

I have found the line (in src/server.rs, as indicated in the error message) where the error message comes from, but due to my lack of rust knowledge, I can't quite understand what it does (and thus exactly why it gives me an error).

If you could tell me what is failing in server.rs, I could maybe resolve this issue by myself.

[Desdaemon]

It's trying to read workspace-specific configuration a la VSCode, but I doubt this is implemented outside of it so it just returns null for all workspaces.