Skip to content

Add underage to the player type - #22

Merged
yung-madamm merged 1 commit into
mainfrom
feat/player-underage
Sep 25, 2026
Merged

yung-madamm merged 1 commit into
mainfrom
feat/player-underage

Conversation

@yung-madamm

@yung-madamm yung-madamm commented Sep 25, 2026 •

Copy link
Copy Markdown
Contributor

What & why

Operators in some markets have to enforce age rules per player, not just per team. The REST API exposes underage on competitors today; the next producer release adds it to the player element on GET /v1/sports/{language}/players/{urn}/profile. This declares it: optional xs:integer, same -1 unknown / 0 no / 1 yes encoding as team@underage. Players nested under competitor_profile share the type, so they carry it too.

Additive → MINOR, tag v1.1.0 after merge. Fixtures updated for both endpoints (player_profile.xml = 1, competitor_profile.xml = -1).

Verification

make check (via a temurin:17 container): 31 schemas, 41 payloads, 0 problems.

Consumers: gosdk gets the matching field in oddin-gg/gosdk#67; its schema test follows main, so land the two back to back. javasdk / netcoresdk regenerate bindings on their own schedule; they ignore unknown attributes so nothing breaks.

🤖 Generated with Claude Code

Same -1/0/1 encoding as team@underage. Optional, so an existing
integration ignoring it stays valid. Players nested in
competitor_profile carry it too, since they share the type.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@yung-madamm
yung-madamm merged commit fb1012c into main Sep 25, 2026
4 checks passed
@yung-madamm
yung-madamm deleted the feat/player-underage branch September 25, 2026 12:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants