-
Notifications
You must be signed in to change notification settings - Fork 0
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
Support #tagging within document text #185
Comments
I also had some WIP tests:
I broke them when I changed the structure of the output slightly, but its straight forward to go either way, and I think they are in the right direction. |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I did the work to add tagging in #126 I started with an in-document solution, but ultimately decided to kiss and use just a text box in the header, then do the rest of the integration. To some extent this implies a front matter approach like #127 -- tags would live on the markdown's title lines:
The alternative, which apps like Bear and Apple notes use, is to integrate them directly into the editor. I think this can make sense, although if I actually look at how I us that in practice, I always slap my tags at the very top of the document -- hence my decision to go with the front matter approach. Still, I implemented some of the parsing logic and want to track that here, since I may end up doing this in the future.
After fidgeting with my unified parser setup, and failing to fully grasp how I should overide it so that this works:
Also saving this for context:
I ended up implementing it as a transformer instead:
With the implied useage of:
There are some useful documentations on their side
I then added supporting basic implementations to mdast-to-slate and slate-to-mdast transformers:
The text was updated successfully, but these errors were encountered: