feat(sync): make type tag extraction optional in config#5
Merged
gwenwindflower merged 1 commit intomainfrom Apr 9, 2026
Merged
feat(sync): make type tag extraction optional in config#5gwenwindflower merged 1 commit intomainfrom
gwenwindflower merged 1 commit intomainfrom
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
At present, the tool contains many very specific, idiosyncratic bits of logic based on my personal patterns. As I iterate towards more general use, I'm keeping the ones that I think are solid, but making them optional. "Type Tags" are one of these, uppercased entity tags like
#Bookor#Author, which rematter can transform into a frontmattertypefield. This was default behavior, this PR makes it optional.