Hidden files and folders (incl. use case)

Hello,
from reading forum posts, I am currently concluding that it is impossible to handle hidden (invisible) files with Hazel. Is this correct?
My use case (actually the very first filter I tried to implement) is as follows:
I often get sent folders of source code. Often, users send a zip file, including the invisible subversion meta information folders, which are in each source code folders. Those folders have the name ".svn". My goal is a simple one: Remove all .svn folders from the folders of files I get sent recursively.
My first try therefore looked like this:
Rule #1, "Delete .svn info":
Rule #2, "recurse":
I figured that this set applied to incoming source code folders would delete all .svn folders contained therein. However, in the "Preview Rule Matches" window, none of the existing .svn folders in my test setup are even displayed, not to mention showing their rule status.
What I would suggest is to make it an option whether hidden files/folders should be automatically excluded (certainly the default setting), or if Hazel works on all files for that specific folder rule. I think in the latter case, I can still exclude all important files from being touched by including a first rule in the list that excludes e.g. handling of all known system files or simply do a "exclude if hidden and not '.svn'".
I hope I was able to demonstrate a legitimate use case for re-considering what seems to be the current handling of hidden files.
If I am missing something and I can already easily do what I want with Hazel as it is now, I'd highly appreciate to learn how.
Regards, Christian
from reading forum posts, I am currently concluding that it is impossible to handle hidden (invisible) files with Hazel. Is this correct?
My use case (actually the very first filter I tried to implement) is as follows:
I often get sent folders of source code. Often, users send a zip file, including the invisible subversion meta information folders, which are in each source code folders. Those folders have the name ".svn". My goal is a simple one: Remove all .svn folders from the folders of files I get sent recursively.
My first try therefore looked like this:
Rule #1, "Delete .svn info":
- Code: Select all
If [all] of the following conditions are met
[Full name] [is] [.svn]
[Kind] [is] [Folder]
do the following:
[Move file] to folder: [Trash]
Rule #2, "recurse":
- Code: Select all
If [all] of the following conditions are met
[Kind] [is] [Folder]
do the following:
[Run rules on folder contents]
I figured that this set applied to incoming source code folders would delete all .svn folders contained therein. However, in the "Preview Rule Matches" window, none of the existing .svn folders in my test setup are even displayed, not to mention showing their rule status.
What I would suggest is to make it an option whether hidden files/folders should be automatically excluded (certainly the default setting), or if Hazel works on all files for that specific folder rule. I think in the latter case, I can still exclude all important files from being touched by including a first rule in the list that excludes e.g. handling of all known system files or simply do a "exclude if hidden and not '.svn'".
I hope I was able to demonstrate a legitimate use case for re-considering what seems to be the current handling of hidden files.
If I am missing something and I can already easily do what I want with Hazel as it is now, I'd highly appreciate to learn how.
Regards, Christian