Properties: hide or unhide specific Properties (YAML Front Matter) by default, and show all properties

Feature requests
, , , ,
1

Use case or problem

  • Some of my notes contains a lot of Obsidian Properties (YAML Front Matter).
  • I’d like to keep all the properties, mainly for usage with e.g. Obsidian Bases.
  • When opening a note, I see many properties I don’t “need” directly within the note view, but I’d like to keep them for reference, or while interacting using Obsidian Bases.
  • When opening a note, I also use some properties frequently, hence I don’t want to collapse the whole properties view.

In other words; I use some properties frequently, and some properties rarely.

Proposed solution

  • I’d like to (globally) hide specific properties (by default), so that the property is not displayed in Live Preview (by default).
  • I’d like to simply right click a property, and set “hide” (or “unhide”).
  • I’d like an “option” in Properties view to quickly “show all properties” (if needed), or by using a command to quickly toggle on/off.
  • I do not want to store the “show/hide defaults” in each note; this should be a global setting (personal preference).

(guess you know the best place to store the defaults, but something like a default preference in the types.json (where we store properties type) could be possible).

Example

In my notes for podcast episodes, I have something like below:

created:
reviewed:
tags:
show:
title:
published:
url: 
url_apple:
url_youtube:
url_shownotes:
url_audio:
related:
guests:
thumbnail:
duration:
status:

By default, I don’t need to display e.g. thumbnail, as this property is automatically created using a template (or similarly). That said, I’d like to still keep the thumbnail property, as it’s useful in e.g. Obsidian Bases and card-view (just to illustrate an example).

Related feature requests

  • I found some related FR (some linked below), e.g. by globally hiding properties using custom CSS (or cssclasses), but I did not find any FR suggesting to quickly also “show all properties” again, e.g. when needing to “see everything”, without toggling CSS snippets on/off (though I guess this possibly can be automated as well, e.g. using a command to toggle a snippet on/off).

Links to related requests

2

This functional is present in my plugin Pretty properties, though it is not officially approved yet.

3

For CSS toggle there are at least three ways.

 

Advanced URI:

obsidian://adv-uri?settingid=appearance&settingsection=CSS%20snippets

https://publish.obsidian.md/advanced-uri-doc/Actions/Settings+navigation

Although Advanced URI itself doesn’t provide feature to map that URI to command palette (see Shell commands for example).

 

CSS Editor:

Very versatile plugin that provides these four features for CSS snippets: create, open, delete and toggle.

Create CSS snippet

Opens a prompt to create a CSS snippet in your .obsidian/snippets/ directory. Upon creation, show editor to edit that CSS file.

Open quick switcher

Opens a suggestion modal to create, edit, or delete a CSS snippet. Has similar functionality to the core quick switcher where holding down a secondary key will modify the action that will take place.

  • Press Enter to open the selected CSS snippet, or if no suggestions are available, create a new CSS snippet.
  • Press ⌘Enter to open the selected CSS snippet in a new tab.
  • Press ShiftEnter to create a new CSS snippet.
  • Press Tab to toggle the enable/disable state of the selected CSS snippet.
  • Press ⌘Delete to delete the selected CSS snippet.

Delete CSS snippet

Deletes the currently active CSS snippet file. Only available when viewing a CSS snippet file.

Toggle the enabled/disabled state of CSS snippet

If the currently active CSS snippet file is enabled then disable it, and vice versa. Only available when viewing a CSS snippet file. Note that you can also toggle this state directly from the quick switcher using the Tab key.

https://github.com/Zachatoo/obsidian-css-editor

 

Snippet Commands:

Not very cool plugin but it maps all of your CSS snippets to commands. Obviously this populates your command palette.