Simplistic file filtering - SPIKE DO NOT MERGE #10
Conversation
This file contains hidden or 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
dgou
commented
Jul 8, 2023
| Include: plugins/buttons | ||
| Exclude: plugins/buttons/styles.css | ||
| Include: plugins/tag-wrangler | ||
| ''' |
There was a problem hiding this comment.
This sample list is to show exluding a tree and then including parts (plugins/buttons) and then excluding parts of that. For a real set of directives, there is no point in excluding plugins and then re-including buttons and tag-wrangler, those would just be straight up includes.
This is of course based on my own test vault.
If we decide to go this route, I would add a self-test for this part of the code.
This was referenced Jul 8, 2023
|
This code has been effectively merged into and adapted to #12 so closing this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Super spikey, but I had a brain storm.
@peterkaminski see the comments in this stand-alone file for how to run it.
I almost did a gist instead, but I wanted easier tracking of comments/changes from draft PR.