Use case or problem
I am trying to build a plugin that uses custom types for frontmatter, which is a big enough endeavor, but I’ve found that the only thing stopping me from completing my madness is to have the ability to style the frontmatter input fields to accomodate my data types’ syntax. Currently, there are no identifying attributes on the frontmatter to distinguish fields from one another (aside from alias, and tag).
Proposed solution
I wanted to use the decorator interface to make it render very specific text for this, but I realize that may require a whole restructuring of the obsidian architecture, but I figure adding simple data-* props, or a class name to the input areas which derive from the property name would be sufficient, and would enable countless others to establish their own types within the front matter.
Current workaround (optional)
Just using the raw text input and handling any rendering discrepencies within the body by binding the data in the frontmatter to a decorator within the body of the document. Not elegant, but works for now.