-
Notifications
You must be signed in to change notification settings - Fork 53
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
Use custom search expression #63
Comments
Definitely having a It is also important to make sure that then those two won't collide. Probably it makes it sense to skip the other if one is provided. @ingalless do you have some thoughts about it? @viktomas BTW thanks for taking the time to make so detailed issue with code examples. I appreciate it a lot! |
I have a folder with old versions of my notes which is in my .gitignore - it would be nice to have an option to respect the |
Problem
Currently, we use
vscode.workspace.findFiles('**/*.md')
to find all fiels that we are about to parse (parse.ts
)This finds files in the whole workspace which might not be desirable. My particular use case is that I've got two folders in my workspace:
permanent
notesreference
notesThe
permanent
notes are about a particular topic and thereference
notes are notes taken from a book or an article.permanent
notes are almost always linking toreference
notes (i.e. saying that I learnt that particular information in book XYZ).The current parsing mechanism results in showing huge clusters of notes all linked by
reference
note (a book or an article) whilst I'm only interested in the connections betweenpermanent
notes.Suggested solution
We could allow users to configure the
findFiles
expression. So instead ofparse.ts
we would use the configured value and only if that's missing, we would default to the current expression:
This would be the most performant solution, but we could as well introduce some allow/deny list that would be used when we iterate through the
findFiles()
result:How does this sound @tchayen ?
The text was updated successfully, but these errors were encountered: