Adopt improved DocumentSymbolProvider API
See original GitHub issueWith the 1.25 release we have finalised the API for the outline tree. A DocumentSymbolProvider
should now return document symbols which can represent a hierarchy and that can differentiate between the full range of a symbol and the selection range, e.g. the name of a function.
Note that we synthesise trees using range-containment when a provider returns SymbolInformation
-objects and that that isn’t perfect. Adopting the new API makes the outline more robust and support features like follow-cursor and diagnostics association.
Let me know if need more information is needed. Happy Coding!
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (8 by maintainers)
Top Results From Across the Web
Language Server Protocol Specification - 3.17
This document describes the 3.17.x version of the language server protocol. An implementation for node of the 3.17.x version of the protocol can...
Read more >5 Ways to Increase API Adoption | ProgrammableWeb
A look at five strategies used to increase API adoption. These are based on principles of marketing, sales, customer service and brand ...
Read more >monaco-editor | Yarn - Package Manager
The Monaco Editor is the code editor which powers VS Code, with the features better described here. Please note that this repository contains...
Read more >CHANGELOG.md - code room
Various editor improvements, such as an option to `renderFinalNewline`, ... resolveCompletionItem` have been modified to better reflect the API of VS Code.
Read more >VS Code API | Visual Studio Code Extension API
Visual Studio Code extensions (plug-in) API Reference. ... DocumentSelector, provider: DocumentSymbolProvider, metaData?
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yeah, there is currently a backwards compatibility challenge. It’s tracked here and will be tackled this month: https://github.com/Microsoft/vscode/issues/57984
Yes, you need to populate the children