1.3.0

Added

• Suggestions of the property names already used in the vault while a property list is typed in a template row. The list of suggestions narrows as you type, a name is chosen with the mouse or the keyboard — arrow keys and Enter, Esc to dismiss — and choosing one inserts the whole name. Suggestions are made for the property the caret is in, whichever place it has in the list, so a name typed after a comma is completed like the first one; names already present in the same field are left out, since repeating a name has no effect on the order. Nothing has to be accepted: a property the vault does not have yet is typed as before, and the stored comma-separated list keeps its format and is read exactly as it was.
• The names come from the frontmatter of the notes Obsidian has in its metadata cache, so no note is read from disk, and the suggestions follow the vault as its notes change. Obsidian's own suggestion component does the filtering, the ranking and the highlighting, which is what makes the field behave like the one the app shows when a new property is added to a note.

1.2.0

Changed

• Obsidian 1.13.0 is now the minimum required version, raised from 1.6.6. The settings are declared with the settings API introduced in 1.13.0, which is what makes them reachable through the search in Settings. Vaults on an older Obsidian keep whatever version they have installed and are not offered the update.
• The Folder templates list is now a list of settings declared to Obsidian, so its add, delete and reorder controls are the app's own and behave as they do in the rest of the settings; the move up and move down buttons the plugin used to draw are gone. A row still holds the folder field and the property list side by side, and existing settings are read unchanged — nothing has to be reconfigured.

Removed

• The plugin's own move up, move down and delete buttons on a template row, along with the styling they needed. Obsidian provides those affordances for a declared list of settings.

1.1.0

Added

• The Process all notes on vault startup setting, off by default, deciding whether the batch run happening once per vault load takes place at all. With it on the run behaves as it did before: it starts after the workspace is ready and the metadata cache has finished its initial build, and shows a notice only when notes were updated or errors occurred. The setting is saved with the rest of the settings and is read when the vault is loaded, so switching it on takes effect the next time the vault is opened.

Changed

• Notes are no longer processed when the vault is opened unless Process all notes on vault startup is turned on. Both commands keep working exactly as before, whatever the setting is.

1.0.0

Added

• Sorting of the YAML frontmatter properties of a note into the order described for its folder. Values, property names and their casing are left untouched, and the content after the frontmatter is never rewritten.
• The Folder templates setting, an ordered list of rows. Each row is a folder together with a comma-separated list of property names in the order they are meant to be written, and has Move up, Move down and delete buttons; the folder field suggests the folders of the vault. Changes are saved as they are made.
• A template applies to every Markdown note lying directly in its folder and in any of its subfolders, so a template for Projects covers both Projects/note.md and Projects/Test/note.md. Path segments are respected, which keeps Projects from matching Projects-old/note.md, and an empty folder path means the root of the vault and matches every note, which makes it a general fallback.
• Templates are checked from top to bottom, and the first one matching a note wins: the more specific folders belong above the general ones. A note no template matches is never processed.
• Properties listed in the chosen template come first in the order of the template, and every other property of the note follows them, keeping its original relative order. A note whose frontmatter is already in the required order is not written again.
• The Create missing properties setting, off by default. With it on, every property of the chosen template the note doesn't have is created with an empty value, and the required order is applied afterwards. Property types are left to Obsidian: the plugin never assigns or changes one.
• The Unlisted properties setting, deciding what happens to the properties a matching template doesn't list: Keep all removes nothing, Remove if empty removes the ones without a value, and Remove all leaves the frontmatter with the properties of the template only. A property counts as empty when it is null, an empty string, a string of spaces, an empty list or an empty map, so false, 0 and dates are values rather than empty properties. Properties the template lists are never removed, even when they are empty.
• The "Sort properties in all notes" command, processing every Markdown note a template matches and reporting what it did: Property Organizer: 3 notes updated, 12 unchanged, 40 skipped, 0 errors. Notes counted as skipped are the ones not processed at all — no template matched them, or they have no frontmatter while Create missing properties is off.
• The "Sort properties in current note" command, processing the note of the active Markdown view and saying whether no template matched it, whether its properties were already organized, or that they have been sorted. The command is unavailable when the active view is not a Markdown note.
• A batch run happening once per vault load, after the workspace is ready and the metadata cache has finished its initial build, without blocking the interface. Writes made by the plugin do not start it again, and a notice appears only when notes were updated or errors occurred. Notes are never sorted behind the user's back when they are created, edited, renamed or moved.
• A note with frontmatter Obsidian cannot read is skipped, counted as an error and reported in the developer console, so the rest of the batch carries on.
• Mobile support. The plugin uses the public Obsidian API only — no Node.js, Electron or direct file-system access — processes notes one after another so that a large vault does not flood the device with parallel writes, and reorders the rows of its settings with buttons rather than drag-and-drop, which works with touch as well as with a keyboard.