Add support for .tid files (TiddlyWiki5) #1390
Merged
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
Contributor
Author
|
Meanwhile five weeks have passed and this PR didn't get a single comment. Are there any reasons for not merging? |
Anteru
requested changes
Apr 10, 2020
Contributor
Author
|
@Anteru : Thanks for your review. I hope everything is okay now. Just tell me if you need further changes. |
Contributor
Author
|
@Anteru : Can this PR be merged, please? |
Contributor
Author
|
Thank you! 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 PR extends the markup lexer by support for .tid files (TiddlyWiki5).
TiddlyWiki has it's own syntax. When it is used in it's Node.js variant, every article ("tiddler") is being saved as a .tid file. A tid file can contain WikiText syntax, TiddlyWiki macros as well as HTML tags, CSS style blocks and usually some meta data.
This is how the example file looks like when it's rendered with the new lexer: