It would be great to have a cache system.
If a file was analysed before and didn't change since this time, we don't have to analyse it.
Also a --no-cache option must be added to get rid of this system.
Question: Where to store the cache? On the project folder (where the phpav command is run)? On a home special directory (e.g.: ~/.phpav/cache)? I think the second option would be better.
Composer and php-cs-fixer cache system would be a good inspiration.
We can store the cache with this way:
- Key: The md5 of the file to compare with the queued one.
- Content: A serialization of a class containing analyse information (infected, not infected, why...)
This will allows to increase the speed of the script.
It would be great to have a cache system.
If a file was analysed before and didn't change since this time, we don't have to analyse it.
Also a
--no-cacheoption must be added to get rid of this system.Question: Where to store the cache? On the project folder (where the phpav command is run)? On a home special directory (e.g.:
~/.phpav/cache)? I think the second option would be better.Composer and php-cs-fixer cache system would be a good inspiration.
We can store the cache with this way:
This will allows to increase the speed of the script.