Skip to content

Conversation

@blakedietz
Copy link
Owner

When renaming a tag with hierarchy, if the root node was renamed, when
removing the path to the node, parents would not be properly cleaned up.

blakedietz and others added 13 commits February 9, 2019 12:47
* docs(logo): Add logo

* build(config.yml): Add release branch
Sort the tag tree alphbetically first by tags, then by file.

Resolves #11
* Scan files asynchronously
* Only include markdown files
- make treeDataProvider use vscode the findFiles function for searching
    - read files and scan for tags asynchronously
* master:
  feat(File node): Add support for opening file from file node (#36)
  docs(README): Add a gif in the readme
  fix(File tree): Only allow markdown files in the tree (#27)
  fix(icon.png): Renames nested-tags-logo.png to icon.png (#23)
  feat(Sorting): Sort the tag tree by tag and file (#22)
When renaming a tag with hierarchy, if the root node was renamed, when
removing the path to the node, parents would not be properly cleaned up.

Closes #37
@blakedietz blakedietz merged commit 7949982 into master Mar 28, 2019
@blakedietz blakedietz deleted the develop branch April 24, 2019 16:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants