Frontmatter Properties in Markdown

[thehiddenwaffle]

Description

Currently importing markdown files which have frontmatter YAML at the start does not correctly create/set tags or other metadata in the corresponding Affine page. In order for larger Obsidian vaults to be imported into Affine it would be necessary to have this feature. Obviously some things like timestamps are highly flexible and would require additional work to import into the "appropriate" places in Affine but just having them as string metadata would make Affine much more compatible with frontmatter.

Use case

I have an Obsidian.md vault I would like to bring into Affine but redoing this metadata would be time consuming so I'm currently just not using Affine for now, which is sad because I like it better.

Anything else?

gets imported as

Are you willing to submit a PR?

• [ ] Yes I'd like to help by submitting a PR!

[affine-issue-bot[bot]]

Issue Status: 🆕 *Untriaged

*🆕 Untriaged

The team has not yet reviewed the issue. We usually do it within one business day. Docs: https://github.com/toeverything/AFFiNE/blob/canary/docs/issue-triaging.md

^{_{This is an automatic reply by the bot.}}

[blackgwe]

👍 I would very much welcome it. It should not be complicated to implement this feature

MVP:

• Tags: create if not available; fuzzy (case sensitive, comma separated or as List)
• all YAML Keys as Text Properties

If possible: Try to find the the property type (Numberm Timestams, DateTime)

[hwangdev97]

This is a good idea. We all know that software like Obsidian uses YAML to bind data.

However, considering that the property of the workspace will be used by the whole team together, if some unexpected collaboration issues arise due to the import, it might mess up the data. Therefore, we will carefully consider this feature of bulk creating properties.