Skip to content

Conversation

@Hoblovski
Copy link
Collaborator

@Hoblovski Hoblovski commented Oct 30, 2025

What type of PR is this?

fix issue 114

Check the PR title.

  • This PR title match the format: <type>(optional scope): <description>
  • The description of this PR title is user-oriented and clear enough for others to understand.
  • Attach the PR updating the user documentation if the current PR requires user awareness at the usage level. User docs repo

(Optional) Translate the PR title into Chinese.

修复 issue 114

背景:

  • 直接问题:为了更好的解析 Python,我在自己本地把 pylsp 换成了 jedi-language-server 。但是解析出来的结点 Content 不对,本应该包含函数体的只包含了函数名。
  • 根本原因:Content 是通过 DocumentSymbol 返回的 location 字段计算来的,jedi 返回的 location 字段只包含了函数名。
  • 解决:为了得到整个函数体,需要使用 range 字段,这就需要开 hierarchicalDocumentSymbolSupport 。然后发现从 2 月到现在它都是错的 (issue bug: wrong ClientCapabilities in LSP initialization #114),所以修了。

暂时去掉了 java 的 go test,因为下载 jdtls 老被限流挂掉

(Optional) More detailed description for this PR(en: English/zh: Chinese).

en:
zh(optional):

(Optional) Which issue(s) this PR fixes:

(optional) The PR that updates user documentation:

@Hoblovski Hoblovski changed the title (draft) fix: make hierarchical docsyms right fix: make hierarchical docsyms right Oct 30, 2025
@Hoblovski Hoblovski force-pushed the fix/hierarchical-doc-syms branch 2 times, most recently from 1a6038e to 4e4b08e Compare October 31, 2025 07:05
@Hoblovski Hoblovski force-pushed the fix/hierarchical-doc-syms branch from 4e4b08e to 46a88b8 Compare October 31, 2025 07:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants