I really would love this functionality so I could make Bases fit my usecase/base structure more succinctly.
x-posting from discord:
My usecase/need is that my workflow is heavily incorporating a parent-child structure of links with various note “types”, so i have an entire relationship graph that i’d looove to filter on.
The simplest example of this/small improvement for significant QOL gain: I’d love to implement flatten over a property key, so that i can map/reduce/filter on whether or not any of the notes above the certain properties.
ex:
currently use domain: [[...]] on notes that links to my company note, or a Client note, or a project, and
currently use context: [[...]] to link create the parent-child tree (more granular – generally agile-related: domain > epic > story > task)
I really want to have a base view that shows me every single note that is a descendant of my company’s note – ideally i’d be able to flatten over domain to coalesce the [[project]], [[client]], [[company]] chain, so i can do a simple filter by contains(flatten(domain), [[company]])
Additional thoughts: Ideally (imo) this example functionality I’ve described just gets baked into Bases-upstream, but I’d argue it’s beneficial to the Obisidan dev team to make bases functions extensible to allow users/devs to hack on what functions are useful for different usecases, and either supply plugins or chatter/share on the discord/forum after trying things out. That way (to reference/appeal to the team) we can help the team determine which functions have usefulness that is ongoing, popular, niche, etc. :^)