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

Update two-way sync note template #110

Open
matthewwong525 opened this issue Jun 16, 2023 · 1 comment
Open

Update two-way sync note template #110

matthewwong525 opened this issue Jun 16, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@matthewwong525
Copy link
Contributor

Is your feature request related to a problem? Please describe.
Allow user to update the two-way sync note-template and add validation to check that it works

@matthewwong525 matthewwong525 added the enhancement New feature or request label Jun 16, 2023
@matthewwong525 matthewwong525 transferred this issue from fleetingnotes/fleeting-notes-flutter Jun 16, 2023
@Zortecatua
Copy link

I have a yaml field that goes in all my notes and helps me organize my notes by content. This I award in Obsidian.
I want the title not as a yaml field but as a heading (#) in the note under the yaml front matter.
I would like to be able to edit notes in FleetingNotesApp folder until they are ready to be included in my usual folder structure.
When I move a note from the FleetingNotesApp folder to another folder in Obsidian, I want that note to be deleted in FN as well, without having to enter a deleted field in yaml.
Example: I was listening to a podcast on my mobile phone today and made notes in the FN Android app at the same time. Then I was interrupted. Some time later I sat at the PC and revised the note (yaml frontmatter and content). In the afternoon I wanted to continue listening to the podcast and start taking notes in the Android app again. All this is only possible with two-way sync. However, I cannot then equip the template with my yaml fields. However, with one-way sync, my Obsidian changes would be overwritten again.
I hope I was able to make clear what I'm talking about. And I hope my English (with the help of Google Translate) is understandable.

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

No branches or pull requests

2 participants