Feature Request: Use multiple Vault directories for fileClass definitions

[zombiemaker]

Feature Description

Add the capability to use multiple or all directories within an Obsidian Vault to define Metadata Menu file classes

OPTION 1: Multiple Directories

• In Obsidian Settings > Community Plugins > Metadata Menu > FileClass settings > Class Files path:
  • Instead of allowing only a single path to be added allow multiple paths to be added
  • Use specified paths for creating list of available file classes

OPTION2: New Obsidian file type for MetaData Menu file class definitions

• Similar to Obsidian canvas files (i.e. files within the Obsidian vault file system directory with .canvas file name extension), define a new file type with a file name extension for Metadata Menu fileClass definitions (e.g., .metadataMenuFileClass)
• MetaData Menu searches for and tracks files with the file extension to add / remove from list of defined file classes
• Use that list to provide options of available file classes

[mdelobelle]

Hi could you detail your use case a little bit? As of today the indexing of file cost a lot in performance, and keeping the fileclasses in a given directory is a way to reduce the nned to parse the whole vault to find fileclass definitions

[zombiemaker]

Thanks for responding! I have 2 use cases:

Use Case 1: Content within an Obsidian vault are organized folder-wise by domains. Each domain has its own folder to act as a namespace. Within each domain, types of domain concepts are defined. Some of them might be used to define additional vault notes to represent instances of those types. Domain concept types would have note / file properties that can be used when defining instances of those types . In such cases, it would be nice to be able to use something like Metadata Menu file classes to define note / file property templates associated with the types.

Use Case 2: I have multiple Obsidian vaults each with their own Metadata Menu file classes. I use Git and GitHub to version control and distribute copies of the vault and collaborate with others. I use the Git submodule feature to "import" one Obsidian vault / Git repository into other Obsidian vaults / Git repositories. This way I can share content between vaults and minimize duplicating the maintenance of content needed across multiple vaults.

In this scenario, I'd like to use the Metadata Menu file classes defined within the "imported" vaults / Git sub-repositories and within the "importer" vault / Git super-repository.

Let me know if additional clarification is needed. Thanks!

[takajasu]

My usecase would be to have a shared section in the vault where shared class definitions should apply and the other part of the vault where my private definitions reside.

An idea would be to be able to supply multiple directories in the config section