Since Fractor 0.5, there is a cache that prevents Fractor from reprocessing unchanged files, potentially leading to performance improvements.
This cache however does not respect the configuration, so when run repeatedly with different config files or after config changes, it will not reprocess any files that were not changed as well.
IMO there is a few ways to deal with this situation:
- in the short term, disable the cache by default
- mid-term, add some kind of hashing to the configuration and store that together with the rest of the cache
Since Fractor 0.5, there is a cache that prevents Fractor from reprocessing unchanged files, potentially leading to performance improvements.
This cache however does not respect the configuration, so when run repeatedly with different config files or after config changes, it will not reprocess any files that were not changed as well.
IMO there is a few ways to deal with this situation: