Add ARMSX1/ARMSX2 smart cache support - #88
Open
misantronic 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
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.
Adds
Armsx1SmartCacheStrategyandArmsx2SmartCacheStrategy, sharing one query helper, that pull recently played games from ARMSX2'sRecentGamesContentProvider(name, SAF/file URI, serial, lastPlayed). Unlike WatermelonDS, ARMSX2 doesn't precompute an RA hash, so these candidates go through the normal hash-then-lookup path instead of a bypass.Also fixes
toAbsoluteStoragePath()to handlefile://URIs, not justcontent://. ARMSX2's provider returns plainfile://paths (since it can write freely to its own storage without SAF), and those were falling through unresolved.Depends on ARMSX2 exposing that provider: ARMSX2/ARMSX2#566.
Verified end-to-end against a side-by-side ARMSX2 DEV build: a PS2 game with a non-RA-recognized dump correctly produced a real "no match" from RA's own gameid API (proving the hash+lookup pipeline, not a bug), and a second game (OutRun 2006) matched and cached successfully (RA gameId 20859), confirmed directly in the local database.
Tracked in #33.