Use cover source for legacy remote cover validation - #52
Open
sigilabcodex wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Updates cover URL validation so the legacy remote-cover metadata path uses
cover.sourcewhen present, falling back to the album provider only when the cover does not declare its own source.Why
An Internet Archive release may use a direct HTTPS cover URL for lab/smoke testing or mirrored artwork without changing the release identity. Previously the sideload cover path honored
cover.source, but the legacy_campwp_remote_cover_urlpath still validated against the album provider.Tests