[UUID Migration] Phase 3 - Prefer UUID Identifiers #29

Closed
opened 2026-06-14 12:11:12 +02:00 by Sansan · 1 comment
Owner

Update application to use UUID as primary identifier. Optional: Add UUID-based GET queries and ensure UUID in API responses.

Acceptance Criteria:

  • UUID-based GET queries added
  • API responses include UUID
  • Backward compatibility maintained
  • All tests pass

Depends on: Phase 2 must be deployed first

Update application to use UUID as primary identifier. Optional: Add UUID-based GET queries and ensure UUID in API responses. **Acceptance Criteria:** - UUID-based GET queries added - API responses include UUID - Backward compatibility maintained - All tests pass **Depends on:** Phase 2 must be deployed first
Author
Owner

Done in 2c3e971 (Prefer UUIDs in the API), which is on develop. The commit says "Closes #29", but Gitea only closes issues from commits on the default branch, so closing it by hand. The remaining cleanup is #31.

Done in 2c3e971 (Prefer UUIDs in the API), which is on develop. The commit says "Closes #29", but Gitea only closes issues from commits on the default branch, so closing it by hand. The remaining cleanup is #31.
Sign in to join this conversation.