Skip to content

fix: remove the checking if metadata are already cached by filename #17

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bfintal merged 2 commits into from
Jan 19, 2026
Merged

fix: remove the checking if metadata are already cached by filename #17

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
eacea42
fix: remove the checking if metadata are already cached by filename
Arukuen Dec 10, 2025
bcfc1f9
Merge branch 'develop' into fix/8-same-name-metadata
Jan 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 0 additions & 8 deletions src/shared/metadata-saver.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,14 +22,6 @@ export const saveMetadata = _metadataArray => {
return Promise.resolve()
}

// Check if all metadata entries are already cached (by filename)
const allCached = metadataArray.every( entry => getCachedMetadata( entry.filename ) )
if ( allCached ) {
// eslint-disable-next-line no-console
// console.log( 'Metadata already saved successfully for all filenames:', metadataArray.map( m => m.filename ) )
return Promise.resolve()
}

// Mark all as successful in cache, keep a local copy of the metadata
metadataArray.forEach( entry => {
if ( entry.filename ) {
Expand Down