Open 36grad opened 5 months ago
Hi @36grad Again, Thanks for this PR.
Can I ask you for a change in approach to the problem?. Instead of adding a force option, (which ultimately resets the file), wouldn't it be better to add an option to face:reset to reset files? 🥲
Yep, that is a good suggestion - I had worked initially based on the PHP code from the appstore version and when I pulled the latest source from the repository I saw that I had to add a code line where I reset the file's status - so this would have been a good approach in the first place. There's one thing, however, which I would be missing is having the option to explicitly analyze those files. If they're only reset there's still a huge number of files to be analyzed there's no way to tell when the reset files will be analyzed. Any ideas here?
If they're only reset there's still a huge number of files to be analyzed there's no way to tell when the reset files will be analyzed. Any ideas here?
MMm.. 🤔 In any case you could add a --path option and you become a hero!. :wink: In the end you will reuse a lot of what you made, but IMHO it makes makes more sense to reset and scan explicitly instead of forcing something.
Add an option (--force_analyze_files) that enablee the user to explicitly (re-)analyze specific files.