PLUG-4682: Fix extra-time/penalty results in World Cup match data streams#91
Open
TimWheeler-SQUP wants to merge 1 commit into
Open
PLUG-4682: Fix extra-time/penalty results in World Cup match data streams#91TimWheeler-SQUP wants to merge 1 commit into
TimWheeler-SQUP wants to merge 1 commit into
Conversation
The match data streams read only score.ft (the 90-minute score) from the openfootball feed, so knockout matches decided in extra time or on penalties showed the wrong result — most visibly for England (e.g. the 2026 QF vs Norway, won 2-1 in extra time, shown as 1-1 and a Draw). matches.js, knockout.js and last-match.js now prefer score.et over score.ft and append the penalty shootout result, e.g. "1-1 (4-3 pens)". last-match.js also decides Win/Loss/Draw from the shootout when present. Bumps worldcup2026 to 1.2.2. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI (base), Organization UI (inherited) Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (4)
📝 WalkthroughWalkthroughThe World Cup scripts now prefer extra-time scores, append penalty shootout results, and derive last-match outcomes from shootout winners. Plugin metadata is updated from version 1.2.1 to 1.2.2. ChangesWorld Cup score handling
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
Comment |
🧩 Plugin PR Summary📦 Modified Plugins
📋 Results
🔍 Validation Details✅
|
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.
📋 Summary
The World Cup match data streams read only
score.ft(the score after 90 minutes) from the openfootball feed. For knockout matches decided in extra time or on penalties, this shows the wrong result.Most visible for England — e.g. the 2026 Quarter-final vs Norway (
{"ft":[1,1],"et":[1,2]}) was shown as 1-1 and reported as a Draw, when England actually won 2-1 in extra time.The fix updates the three knockout-capable scripts to prefer
score.etoverscore.ft, and to append the penalty shootout result when present (e.g.1-1 (4-3 pens)).last-match.jsnow also decides Win/Loss/Draw from the shootout rather than the pre-shootout scoreline. Group-stage streams are unaffected (group games can't go to extra time/penalties). Plugin bumped1.2.1 → 1.2.2.Verified by running the post-request scripts against the live 2026 feed and the completed 2022 feed (Argentina final
3-3 (4-2 pens)/ Win; France3-3 (2-4 pens)/ Loss), and end-to-end viasquaredup testagainst a deployed instance.🔗 Related issue(s)
🧩 Plugin details
worldcup2026)Does this PR introduce any breaking changes?
📚 Documentation
✅ Checklist
🤖 Generated with Claude Code
Summary by CodeRabbit
Bug Fixes
Chores