fix(outline): use the correct symbols and filter config format #3924
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is this PR for?
The symbols-outline extra was removed in favor of outline.nvim in #2535 (thanks!), but the configuration for symbols in outline.nvim is not backwards-compatible.
This fixes the configuration for the symbols icons and filter to be usable by outline.nvim.
Does this PR fix an existing issue?
It doesn't seem like anyone has encountered this issue, but I can confirm that the config currently used by LazyVim is incorrect. The symbols table is at
symbols
for symbols-outline.nvim, but it's now atsymbols.icons
for outline.nvim.There is no such
symbols_blacklist
key. Instead,symbols.filter
is used, which is a kind of "whitelist".Coincidentally, outline.nvim fully supports the LazyVim
kind_filter
config table structure. It can either be a list of strings (kinds), or a list of strings for each filetype key. Setting to nil or false makes it so all symbols are included, just like in LazyVim.See the docs on the
symbols.filter
structure.Checklist