Open
Conversation
…ing instead of incremental string concatenation.
…in fixListIndentation (frontmatter fence and code-fence detection) and removing the redundant trim() in tag extraction.
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
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.
This is intended to fix several issues I was having with the Bear importer.
I tested these changes by running my Bear export of +1600 notes through the changes over and over. My settings for the import were to to flatten nested tags and not to store note identifiers in front matter. The "flatten" option may have side-effects, but from what I understand, as Bear user, I would not expect that sort of result.