feat(#3119): Expose filter functions to the api

[gracepetryk]

Addresses #3119. Filter methods have all been normalized to accept a single path variable so that they may be easily called during a call to custom. Results are cached based on the path argument during each render loop to avoid computing filters more than once if the filter is enabled and also called in custom.

This enables filter configurations that were not possible before, for example combining filters so that items are only filtered if they match both:

require('nvim-tree').setup({
  filters = {
    custom = function (path)
      local filter_api = require('nvim-tree.api').filters

      return filter_api.git_clean(path) and filter_api.no_buffer(path)
    end
  }
})

[alex-courtis]

Nice work! I'll get to a proper review / test in the next couple of days.

[alex-courtis]

Apologies for the delay, my time is limited right now.

This deserves considerable review and test time which I hope to have in the next few days.

[alex-courtis]

It's working nicely with a variety of composed filters and tests on path, with toggle_custom_filter working as expected.

Unfortunately this one's not updating until we manually refresh:

  filters = {
    enable = true,
    git_ignored = false,
    dotfiles = false,
    git_clean = false,
    no_buffer = false,
    no_bookmark = false,
    custom = function(path)
      return path:match(".*Makefile") and not api.filters.no_buffer(path)
    end,
    exclude = {},

no_buffer requires the Buf:filter_buffer_ event in Explorer to apply the filter, and it's only fired when no_buffer = true.

Possible solution: fire the event when the user has a custom function. That's not the best for performance, happy for any other ideas.

[alex-courtis]

This wasn't you, but we need to change the description of the default mapping Hidden->Custom

  vim.keymap.set("n", "U",              api.tree.toggle_custom_filter,      opts("Toggle Filter: Hidden"))

[alex-courtis]

I think we can go one step further with the custom function: pass a node instead of a path, allowing the user to see the type, stat, children etc.

All of the filters could take a node, for consistency and ease of use, as well as aiding any future builtins.

There is extra complexity: we need to supply the user with a sanitised node rather than the actual, as per Decorator. See their cached creation: https://github.com/gracepetryk/nvim-tree.lua/blob/ea5097a1e2702b4827cb7380e7fa0bd6da87699c/lua/nvim-tree/renderer/builder.lua#L236-L238

[gracepetryk]

Thanks for the review! I'll have a chance to go over your comments and make changes within in the next few days.

[alex-courtis]

Any progress on this one @gracepetryk ?

Would you like me to complete this and merge it?

No pressure...

[gracepetryk]

Hi @alex-courtis, I haven't had the time to work on this I thought it would. If you'd like to complete + merge it go ahead :)