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
There's this capability in LSP where a server can be a foldingRangeProvider. An editor can ask the server to provide folding ranges.
It is at the moment not possible to bring those fold ranges to the gutter area.
Preferred solution
A new ST callback, much like on_query_completions, where a plugin must return a promise object to provide new fold regions. All fold regions from all plugins are merged in some way or another.
If a region is replaced entirely inside of a fold region, then the fold region can just shrink/expand, no?
If a region is replaced entirely outside of a fold region, then the fold region can move.
If the replacement region intersects with the fold region endpoints, then yeah the fold region becomes invalid/stale.
In any case, requesting after a view is saved was just an idea. It's not a hard requirement for me.
Problem description
There's this capability in LSP where a server can be a
foldingRangeProvider
. An editor can ask the server to provide folding ranges.It is at the moment not possible to bring those fold ranges to the gutter area.
Preferred solution
A new ST callback, much like on_query_completions, where a plugin must return a promise object to provide new fold regions. All fold regions from all plugins are merged in some way or another.
This way, ST can coordinate when to ask for new fold regions (perhaps after saving the view). And ST can also merge results.
Alternatives
None.
Additional Information (optional)
This is one possible solution for #101
The text was updated successfully, but these errors were encountered: