🐛 Fix logical error preventing force rebuild scans #574
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes a small logical error that prevented the scan options from being considered when a modified timestamp could be extracted from a file on disk. This allows for the scan options to be considered but, as I mentioned on Discord, options will force a full rebuild of every book and corresponding metadata for the library. This is why I didn't expose it on the UI yet, that will be properly implemented by https://github.com/stumpapp/stump/tree/al/granular-scans.
I verified this fix by creating a library without koreader hashes enabled, enabling it, then running a scan with
force_rebuild
:API keys are from my local development instance so it doesn't matter