Summary
Add support for including specific filenames (or filename patterns) in the Workspace Wiki file discovery, even when their extension is already covered by another rule.
🔍 Problem
Currently the extension discovers files based on extensions only (via workspaceWiki.supportedExtensions).
This works well for typical documentation formats like .md, .txt, etc., but for some languages you might have source files that should be included in the wiki view because they serve as documentation.
Example:
- A file like
doc.go in a Go project
- This file is intended to be documentation, not normal source
- But including
.go in supportedExtensions would show all Go source files, which is not desirable
So we need a way to include specific file names or name patterns in addition to extension-based discovery.
🧠 Example Use Cases
| Use Case |
Desired Behavior |
doc.go exists |
Show doc.go in wiki tree, without showing all .go files |
Pattern like *.guide.ts |
Show only files matching the pattern |
Summary
Add support for including specific filenames (or filename patterns) in the Workspace Wiki file discovery, even when their extension is already covered by another rule.
🔍 Problem
Currently the extension discovers files based on extensions only (via
workspaceWiki.supportedExtensions).This works well for typical documentation formats like
.md,.txt, etc., but for some languages you might have source files that should be included in the wiki view because they serve as documentation.Example:
doc.goin a Go project.goinsupportedExtensionswould show all Go source files, which is not desirableSo we need a way to include specific file names or name patterns in addition to extension-based discovery.
🧠 Example Use Cases
doc.goexistsdoc.goin wiki tree, without showing all.gofiles*.guide.ts