Skip to content

[WIP] API: Full tournament endpoint#2620

Draft
tienne-B wants to merge 3 commits intodevelopfrom
api/full-export
Draft

[WIP] API: Full tournament endpoint#2620
tienne-B wants to merge 3 commits intodevelopfrom
api/full-export

Conversation

@tienne-B
Copy link
Copy Markdown
Member

No description provided.

tienne-B added 2 commits May 1, 2025 22:16
As a replacement for DebateXML, we could attempt to use a nested
structure with our existing API serializers as a base for the export and
archival of Tabbycat data.

This approach will improve maintainability as more functionality can be
achieved with less code, and that code is re-usable.

The challenge is how to handle imports through this endpoint, as it
would have to be possible to import data with lateral foreign keys (say
participants in a pairing), but these keys would be different once
created.
@tienne-B tienne-B force-pushed the api/full-export branch from 3324423 to 9952e2e Compare May 2, 2025 01:16
@tienne-B tienne-B linked an issue Oct 3, 2025 that may be closed by this pull request
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.

Create full tournament export with API schema

1 participant