Cache invalidation when .perltidyrc changes

[szabgab]

If we change the .perltidyrc file we need to invalidate the cache in .tidyall.d/ It can be done manually by running tidyall -a --refresh-cache but how can we communicate this to the other developers and to our CI environment?
In our CI environment we use a cloned repository and thus it has a cache of its own. After we make a change to .perltidyrc we start to get failure reports from the tidyall_ok() call as it does not notice that it should rebuild the cache.

I think tidyall should automatically invalidate the whole cache if the .perltidyrc configuration file is newer than the cached files.

I wonder if there is an option for that or if there is some other solution to this issue?

[autarch]

Sorry I didn't respond earlier. There's no way to do this right now but this should definitely be fixed. There's also #44 which is related.