You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both C# and C++ language servers filter local variables, but some (Python, JS) do not. documentSymbol is used to build outline of a document and local variables are barely useful. I think it should be mentioned in the standard how to treat them. Personally I vote for filtering
The text was updated successfully, but these errors were encountered:
I am personally against stating this in the specification. I have no problems with having an implementation guide line page where we mention good practices but there might be use cases we don't see where it makes sense to include them.
For an alternative perspective, the scripting language I maintain a language server for doesn't have the concept of local variables. It's data oriented and barely has control flow.
For this language, even the SymbolKind enum is an overly restrictive and arbitrary.
If you have a language without functions, variables, interfaces, classes or even arrays: what on earth would I do with a protocol requirement to exclude local variables?
We closed this issue because we don't plan to address it in the foreseeable future. You can find more detailed information about our decision-making process here. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.
Both C# and C++ language servers filter local variables, but some (Python, JS) do not. documentSymbol is used to build outline of a document and local variables are barely useful. I think it should be mentioned in the standard how to treat them. Personally I vote for filtering
The text was updated successfully, but these errors were encountered: