feat(playmatch): move integration to API v2#3689
Merged
Merged
Conversation
gantoine
approved these changes
Jul 7, 2026
Member
|
changed my mind, this is making the cut lol |
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.
Description
Moves the Playmatch integration to the new API v2 endpoints, since v2 is the version going forward. Older clients (pre 5.0) stay supported on v1, they just won't receive new features.
While at it, this also sends the CRC32 hash as an additional identify lookup key, which v2 supports.
Disclosure
I am not a Python developer and am not very familiar with the RomM codebase. I used Claude to help with the endpoint switch and to validate the change against the Playmatch v2 OpenAPI spec. I reviewed the result before submitting.
Checklist
Please check all that apply.
Screenshots (if applicable)
Backend change only, no screenshots needed