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
currently LSP4E (and more and more clients) is using DocumentSymbol to provide an outline.
As first iteration having just the list of routes can be nice
Then having them grouped by Camel context
then having also global endpoint
then... we will see at usage and open new enhancement request
The text was updated successfully, but these errors were encountered:
- allows to find routes more easily
- in VS Code Ctrl+Shift+O
- in Eclipse Desktop with LSP4E provides an outline and with
- limitation: the SymbolKind used is "Field", there is currently an
hardcoded set of possible symbol kind, none are really matching "Camel
routes"
Signed-off-by: Aurélien Pupier <apupier@redhat.com>
apupier
changed the title
Provide outline for Camel routes
Provide outline:DocumentSymbol for Camel routes
May 30, 2018
apupier
changed the title
Provide outline:DocumentSymbol for Camel routes
Provide outline/DocumentSymbol for Camel routes
May 30, 2018
- allows to find routes more easily
- in VS Code Ctrl+Shift+O
- in Eclipse Desktop with LSP4E provides an outline and with
- limitation: the SymbolKind used is "Field", there is currently an
hardcoded set of possible symbol kind, none are really matching "Camel
routes"
Signed-off-by: Aurélien Pupier <apupier@redhat.com>
currently LSP4E (and more and more clients) is using DocumentSymbol to provide an outline.
As first iteration having just the list of routes can be nice
Then having them grouped by Camel context
then having also global endpoint
then... we will see at usage and open new enhancement request
The text was updated successfully, but these errors were encountered: