New Frontmatter configuration is not saved

[xrauphoenix]

What happened?

When creating a new Frontmatter field, the field can be added successfully. However, when I edit this new field and click "Save", the editor window closes, but the changes are not persisted.

For example, I create a new Frontmatter field, give it a name, configure it, and click "Save". The window closes normally, but when I reopen the settings, the new field is either missing or the changes made to it have not been saved.

This makes it impossible to reliably create and configure new Frontmatter fields.

Steps to reproduce

1. Open the Metadata Auto Classifier settings.
2. Click "Add frontmatter".
3. Open the newly created Frontmatter configuration for editing.
4. Enter a new name for the Frontmatter field.
5. Configure the field as desired.
6. Click "Save".
7. Close and reopen the Metadata Auto Classifier settings.
8. Open the Frontmatter configuration again.

The new Frontmatter field and/or the changes made to it are not persisted. The editor closes normally after clicking "Save", but the configuration is missing or has reverted when the settings are reopened.

Expected behavior

Clicking "Save" should persist the new Frontmatter field and all of its configuration.

After closing and reopening the settings, the newly created Frontmatter field should still be present with the exact configuration that was saved.

Plugin version

1.12.10

Obsidian version

1.13.7

Operating system

Windows

Additional context

I am using the plugin with a local Ollama provider and a Qwen3 model.

I first encountered this while trying to configure several independent Frontmatter fields for an Obsidian note-classification workflow (for example Personnes, Domaine, Projet and Logiciels).

Existing Frontmatter configurations can work correctly: I have successfully tested classification with an existing Frontmatter field, including classification using reference values. The problem appears specifically when creating/saving a new Frontmatter configuration.

The behavior is consistent: the editor closes after clicking "Save", but the newly entered configuration is not persisted.

I have also previously encountered an issue where the Ollama configuration appeared to require an API key even though Ollama is running locally. This may or may not be related, but I mention it in case the two problems have a common cause.

Thank you for developing and maintaining this plugin. It is very promising for local-LLM-based metadata classification in Obsidian, and I hope this report helps improve it.