BUG: document_symbols no method get_depth

[BigfootN]

Did you check docs and existing issues?

• I have read all the docs.
• I have searched the existing issues.
• I have searched the existing discussions.

Neovim Version (nvim -v)

0.10.4

Operating System / Version

Archlinux

Describe the Bug

Hello,

I am trying to use the source document_symbols but when I hit enter I get the following message:

document_symbols/commands.lua:21: attempt to call method 'get_depth' (a nil value)

Screenshots, Traceback

No response

Steps to Reproduce

In my case it was a lua file with lua_ls as lsp.

1. Setup the plugin with an empty configuration with document_symbols in the sources
2. Execute the command:

Neotree source=document_symbols position=left

4. Try to hit enter on a symbol in the Neotree with the symbols
5. The error described appears

Expected Behavior

If it is a leaf there should be nothing. If the symbol is a node, the symbol should expand showing it's children symbols.

Your Configuration

{
	sources = {
		"filesystem",
		"document_symbols"
	}
}

[pynappo]

is there a specific lua file you can reproduce this with or does everything error for you? i'm not able to reproduce this for some reason

[BigfootN]

Thank you for your quick response.

No, unfortunately not. As long as the lua file has symbols it's what I observed.

Sorry for not being of more help.

[pynappo]

no worries, i will take a closer look in a few hours. it looks like i may have broken something with merging #1651

[pynappo]

If you have some time, can you test the #1712 PR and see if that helps your issue?

edit: actually, i'll just immediately merge it into main. you can checkout the main branch instead.

[BigfootN]

Thank you. I'll check that tomorrow and open an issue if there's an issue.

Thank you for your time 👍

[onnttf]

If you have some time, can you test the #1712 PR and see if that helps your issue?

edit: actually, i'll just immediately merge it into main. you can checkout the main branch instead.

Hi, I tested with this commit and I don't get this error anymore.