Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Add option to sync title field in the frontmatter yaml #65

Open
jskherman opened this issue Nov 3, 2022 · 6 comments

Comments

@jskherman
Copy link

Feature Request: Would it be possible to add an option to the plugin to both rename the heading and the frontmatter title at the same time? And leave the rest of the frontmatter unchanged?

Something like:

---
id: 20221103121801
title: "Title of the note here to be synced"
aliases: "Something else"
tags: 
  - tag1
  - tag2
---

# Title of the note here to be synced

Curabitur blandit tempus ardua ridiculus sed magna.
Sed haec quis possit intrepidus aestimare tellus.

This would immensely help in the use case where the markdown file is required to have this title field like for use in static site generators like Hugo or Jekyll. I tried having a look with the code but unfortunately, I don't have enough knowledge of Typescript to be effective yet. Thanks.

@dvcrn
Copy link
Owner

dvcrn commented Nov 3, 2022

A "replace all occurrences of the heading" option could be something to consider

@jskherman
Copy link
Author

That would also be good way to go about it, yes.

@lyndhurst
Copy link

I would love to see this feature happening as well, but ideally with an option to disable filename syncing.
I personally use UUIDs as file names like many zettelkasten users, and having a title field is mandatory for many obsidian features.
Thanks for considering.

@bvolkmer
Copy link

I started working on this with the use case I'm interested in most (replacing heading ⇿ filename with front matter ⇿ filename). #71

@bvolkmer
Copy link

bvolkmer commented Jun 1, 2023

I have a working solution in PR #74. As it consists of refactoring and some changes of asynchronous behavior, use with caution. But testing is appreciated.

@dvcrn
Copy link
Owner

dvcrn commented Jun 2, 2023

Thanks Thanks for catching up on this! I'll try to take a look!

Feel free to un-draft it if you think it's ready for review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants