-
Notifications
You must be signed in to change notification settings - Fork 12
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
[WIP] Properly exclude folders #77
Conversation
Hey! Thanks for your work, i marked this PR as a draft while it is still WIP :) |
I just figured out that as the excludedFolders are treated as regex, my suggestion already works. It just has to be proper regex. For example, You can decided if you want to keep it proper regex, or maybe add a little If you want to keep the proper regex, this PR should be ready to merge. Edit: I would change the placeholder in PluginSettingsTab.ts in line 113 to include a line with either |
I think adding the placeholder is a really good idea, mind adding that for me? :) I think most ppl aren't aware that it requires to be a valid regex that matches the entire path to be excluded, maybe even add a message in it that it does infact only support regex |
Sorry I was busy, I added |
Just not sure if its the right move to simply modify the expressions, i think adding more awareness is more important? |
Would just add it in the description of the option i guess |
If you tell me what you want the description to be I can change it to that, I suck at formulating concise descriptions lol |
Closing this in favour of #93 |
I made a very small change, which will properly exclude folders (and therefore somewhat fix #68). This will only exclude the "actual" folder though, subfolders still get treated normally. Depending on use-case, this could be favorable or annoying.
I would propose keeping it this way, and adding some basic form of regex (ie.
media/*
) for also excluding subfolders, but I haven't looked into how that should get implemented yet.