bug: treesitter highlight issue about neovim

[rgruyters]

Thanks for the update and the great help. Eventually went for

require("rose-pine").setup({
      highlight_groups = {
        ["@field"] = { fg = 'text' },
        ["@attribute"] = { fg = 'subtle' },
      },
})

[mvllow]

Sorry, could you elaborate on what exactly you'd like the result to be? Are you saying dataclasses should be different from name, age, etc.?

[rgruyters]

No, type str of name should be a different color as shown in your screenshot. I don't know why it doesn't show in my test. I have used the repro config, but it is not shown in my terminal.

[mvllow]

Ah, those must be from the language server. If you can provide the output of :Inspect on both the variable and the type I can offer more assistance. I’m assuming those groups will start with @lsp

[rgruyters]

There is no @lsp when I view :Inspect.

variable:

Treesitter
  - @variable.python links to @variable python
  - @field.python links to @field python

type:

Treesitter
  - @variable.python links to @variable python
  - @type.python links to Type python
  - @type.builtin.python links to Type python

[mvllow]

Gotcha, thanks for those. This is the same for other languages as well, we set types and fields to foam. Although not ideal, I think for now it's best to modify your personal config:

require("rose-pine").setup({
  highlight_groups = {
    ["@field.python"] = "iris" -- this can be any named palette value
  }
})

It's hard to not have fields be the same colour as some value because the value can be a type (foam), number (rose), string (gold), variable (text), etc.

[rgruyters]

Thanks, unfortunately your solution didn't work. (gives Lua errors)

This one works

require("rose-pine").setup({
  highlight_groups = {
    Type = { fg = "iris" },
  },
})

[mvllow]

I updated my comment above, I was missing square brackets around the key. Glad you got it to work though :)