feat: Basic support for nested tags #268
Merged
Conversation
This file contains 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
artempyanykh
approved these changes
Nov 25, 2023
There was a problem hiding this comment.
Thanks @TheBlob42! Looks good! In future, it should be possible to tune the parser to parse nested tags in a more structured way to support additional use-cases (although, just using workspace symbols with fuzzy matching should go a long way)
|
Thanks, I appreciate adding this! |
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.
fixes #267
As described in the issue this only solves the basic requirements so that nested tags (like in Obsidian) work correctly in terms of references, symbols and auto completion.