The user input is silently not saved if yaml cannot be parsed

[danieltomasz]

Describe the bug

• Create database with a file where yaml is corrupted, for example with title: "title (no quote)
• create a new column, and try to put some value there
• the value is not saved, and there is no notification about an error
  Obsidian 0.15.4, plugin 1.8.2
  Also why the quotes are removed from string ?
  title: "Title" is becoming title: Title

[RafaelGB]

Hi @danieltomasz, the error handler could be improved with notifications, I am agree. I will add them when the react migration its finished.

If the yaml is not well constructed the edition will fail. The unique error already controlled is when the yaml do not exist or there is a duplicate (inline with frontmatter or frontmatter with inline)

[danieltomasz]

Also I was able to identify use cases where plugin fails
For example, someone might use this schema with title title:'@title' single quoted scalar which is a proper yaml entry, but the plugin is failing on it (the title:@title with plain scalar is not a proper yaml)
https://www.yaml.info/learn/quote.html

But I this this is a limitation of how the yaml entries are parsed in your plugin and is hard to do something with it?

One use case when I see this might be a problem is people including bibtex citekey into they bibliographic notes like citekey:'@citekey', which is quite popular use for obsidian, or people using special character like ! into beginning of title to visually categorize the notes

If changes in parsing are not easy to do, maybe documenting what kind of input could be parsed might be useful?

[RafaelGB]

I am using the ParseYaml function of Obsidian + Dataview Inline search for inlines.

The value requires an space after : to work

[danieltomasz]

I think it doesnt work because your plugin strip quotes from scalars,
title: '@title' is a valid yaml entry but title: @title is not
plugin cannot process title: '@title' , and dont save the values in yaml/display them in the table

You could compare results

---
title: title
Topic: topic
---

with

---
title: '@title`
Topic: topic
---

[RafaelGB]

I just test '@value' and works with 1.8.2

Notice that in your sample there are different types of quotes wrapping the value

` instead of '

[danieltomasz]

indeed, sorry for the confusion!

[RafaelGB]

Do not worry, I am happy to help!

About the error handler will takes time. The migration of react-table version and react will take 2 months aprox... But will be worth for sure!