Add support for super noteType #2
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… file to manually copy)
|
Hey!
Is the export done sequencially or all the notes at the same time? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
summary:
added 'updated' to frontmatter yaml
handle noteType super
otherwise the note content just becomes a single-line json mess (which is standard-note's internal representation for 'super' notes)
{"root":{"children":[{"children":[{"detail":0,"format":0,"mode":"normal","style":"","text":"Clip source: ","type":"text","version":1},...should not change anything unless the note-type is 'super'
This probably does not parse everything possible in a 'super' node, but it parses all of my cases.
Cases I didn't handle, show up as text in the .md files
#error: ....(adding those error as a tag seemed like a nice touch)
Anyway, thank you for the script!