mirror of
https://github.com/BoostIO/BoostNote-App.git
synced 2026-04-27 05:15:56 +03:00
[GH-ISSUE #603] Store as notes as .md files #311
Labels
No labels
android 🤖
assigned to core 🦹
bug 🐛
documentation 📚
documentation 📚
duplicate 🚫
external issue 🔼
external issue 🔼
feature request 🌟
funded on issuehunt 💵
help wanted 🆘
improvement request 🔨
improvement request 🔨
ios 🍎
mobile 📱
needs investigation 🔬
needs more info ℹ️
needs specs 📐
plugin idea 🔌
plugin idea 🔌
poll 🗳️
pull-request
question ❓
rewarded on issuehunt 🎁
security issue 🔑
won’t fix ❌
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/BoostNote-App#311
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @tcharlss on GitHub (Aug 28, 2020).
Original GitHub issue: https://github.com/BoostIO/BoostNote-App/issues/603
(Hoping this topic has not been adressed before, I did a quick search and didn't find it.)
Current behavior
Notes are all stored in a single JSON file.
Expected behavior
This might go against the philosophy of the app, but I'm giving it a shot anyway :)
I was expecting the notes to be stored as real independant markdown files.
I think it's important that the actual notes remain easily accessible outside of the app, without needing to export them first.
Having real markdown files would allow us to find and edit them with any other editor, if need be.
Unfortunately, this is a bit of a show stopper for me.
The JSON could be used to store the meta data (tags and such), but for me it's important the actual content of the notes remain in traditional markdown files.
Environment
Desktop/Web
@Rokt33r commented on GitHub (Sep 1, 2020):
Could you tell me why do you need this feature?
@tcharlss commented on GitHub (Sep 1, 2020):
Well to sum it up, that way the notes would not to be "locked" inside the app (regardless of any export feature).
On top of my head:
@Nelvin commented on GitHub (Sep 12, 2020):
I'm switching over to markdown at the moment and also evaluating the (huge amount) of existing tools and to me this is a crucial feature as it helps to decide which tool to use depending on what file I actually work.
One might edit files depending on the current needs with different tools like boostnote or a coders editor (VSCode, Sublime etc.) or maybe generate/modify files using scripting languages (export table data etc.), use tools like imdone.io etc.
@ReneHamburger1993 commented on GitHub (Nov 25, 2020):
For me this feature would be nice too.
For the sake of converting some python examples to a ipython notebook I adapted an existing solutions to export the markdown content from the json files and then be able to convert them.
To directly have those as md files would be great!
@Flexo013 commented on GitHub (Nov 30, 2020):
@ReneHamburger1993 Make sure to leave a 👍 on the first post in this thread to show your interest 😃
@ReneHamburger1993 commented on GitHub (Dec 1, 2020):
got it! 👍
@RyanGreenup commented on GitHub (Mar 8, 2021):
So some reasons I want files and not a database:
@d-luk commented on GitHub (Aug 9, 2021):
For anyone who would like to convert their Boost Note JSON files to plain Markdown (.md) files, I've created a little script to do this: https://gist.github.com/d-luk/449ec392f439396dac40d06bf3362828
@Komediruzecki commented on GitHub (Aug 22, 2021):
Hi, all,
I added this to local space roadmap considerations (will be released soon), there is a similar duplicate here as well: https://github.com/BoostIO/BoostNote.next/issues/811
@Rokt33r should we transfer this issue to boost the note local repository?
@Rokt33r commented on GitHub (Aug 23, 2021):
Duplicated and transferred. Please follow https://github.com/BoostIO/BoostNote.next/issues/603.