Use case or problem
I use an Obsidian Base file with a global filter that only includes notes from a specific folder, for example /notes.
In this Base, I display two columns: name and type.
The type property is used by notes in /notes, and its valid values are limited to atomic or essay.
However, I also have notes outside of /notes that use the same property name (type) with unrelated values (for example, fruit). When I click an empty type field in the Base table, the plugin suggests values from the entire vault, including unrelated ones like fruit.
This makes property suggestions noisy and error-prone when the Base is already scoped to a specific folder.
Proposed solution
Add an option for Bases to scope property value suggestions to the current Base filter or folder, instead of using all values from the entire vault. This would allow property suggestions to better reflect the context of the Base view and reduce irrelevant values.