-
Notifications
You must be signed in to change notification settings - Fork 299
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
excludes doesn't appear to work with subdirectories/paths #553
Comments
I feel like Which means that I believe I need to rewrite this part. I started to POC around this today and will see how it goes but this could be seen as a breaking change though. That said, I'm not sure a lot of users are using |
For example if I have a directory /mypath/folder with subdirectories ``` /mypath/folder ├── folderA │ ├── subfolderA │ ├── subfolderB │ └── subfolderC ├── folderB │ ├── subfolderA │ ├── subfolderB │ └── subfolderC └── folderC ├── subfolderA ├── subfolderB └── subfolderC ``` I would like to be able to start crawling at ``/mypath/folder` and crawl everything except `folderB/subfolderB` for example. I would like to be able to put `"excludes": ["folderB/subfolderB"]` or even a wildcard like `"excludes": ["folderB/subfolder*"]`. Closes #553.
OK thanks. It sure would be useful for me as I have some specific indexes that I’ve built off specific folders, but I’d like to build an “other” index which encapsulates everything else around those directories but excludes the ones I’ve made specific indexes out of. If you need some testing done I’d be happy to try it out for you.
Thanks,
|
@a344254 I removed some personal information from the last answer you sent (email signature). I created this branch https://github.com/dadoonet/fscrawler/tree/fix/553-exclude-dirs which supports the new feature. Compile the project with mvn package -DskipTests And get the zip distribution file. Documentation about this change is:
Let me know! :) |
For example if I have a directory /mypath/folder with subdirectories ``` /mypath/folder ├── folderA │ ├── subfolderA │ ├── subfolderB │ └── subfolderC ├── folderB │ ├── subfolderA │ ├── subfolderB │ └── subfolderC └── folderC ├── subfolderA ├── subfolderB └── subfolderC ``` I would like to be able to start crawling at `/mypath/folder` and crawl everything except `/folderB/subfolderB` for example. I would like to be able to put `"excludes": ["/folderB/subfolderB"]` or even a wildcard like `"excludes": ["/folderB/subfolder*"]`. Closes #553.
I did some testing this morning and it appears to work. Thanks! |
Thanks @a344254. I just forgot to close and release the sonatype repo :) |
For example if I have a directory /mypath/folder with subdirectories
/mypath/folder
├── folderA
│ ├── subfolderA
│ ├── subfolderB
│ └── subfolderC
├── folderB
│ ├── subfolderA
│ ├── subfolderB
│ └── subfolderC
└── folderC
├── subfolderA
├── subfolderB
└── subfolderC
I would like to be able to start crawling at /mypath/folder and crawl everything except folderB/subfolderB for example.
With the way that I believe "excludes" works currently, I could put "folderB" which would exclude all of "folderB", or I could put "subfolderB" which would exclude folderA/subfolderB, folderB/subfolderB and folderC/subfolderB
I would like to be able to put "excludes": ["folderB/subfolderB"] or even a wildcard like "excludes": ["folderB/subfolder*"]
The text was updated successfully, but these errors were encountered: