Skip to content

refactor: Add proposal versioning and team data to users API

Edouard Legoupil requested to merge feature/proposal-dashboard-overhaul into main_dev

Created by: Edouard-Legoupil

This commit incorporates further user feedback to enhance data tracking and API responses.

  1. Proposal Content Versioning:

    • The proposal_status_history table has been enhanced with a generated_sections_snapshot JSONB column.
    • All endpoints that modify a proposal's status (/create-session, /submit-for-review, /request-submission, etc.) have been updated to save a complete snapshot of the proposal's content at that specific moment. This creates a valuable version history for each proposal, which is essential for building an LLM training dataset over time.

  2. Enrich User API Response:

    • The GET /users endpoint has been updated to JOIN with the teams table.
    • The response now includes the team_name for each user, providing more context to the frontend.
  • Does my code meet the quality standards for releasing packages?
  • Does the reviewer have all the information to validate the features/issues without too much research?
  • Does the customer who will validate the associated tickets have the information to do so without wasting time?

Issues to validate to close :

  • issue #

Processed issues to keep open or in progress:

  • issue #

Checklist:

  • Does the package check go local?
  • Does the CI pass?
  • Are the added / fixed features documented, tested?
  • Are the added features / solved problems briefly presented in the PR message?
  • Are the changes related to tickets / issues that I have listed in the commits and in the PR itself?
  • Are the tickets in "review" mode in the Project Tracking Board?
  • Does each ticket, if it is to be closed after acceptance of the PR, contain a comment that tells how to validate it?

Merge request reports