Skip to content

Fix(api): Use proposal_id in regenerate_section endpoint

Edouard Legoupil requested to merge fix-regenerate-section-endpoint into main_dev

Created by: Edouard-Legoupil

The regenerate_section endpoint was previously using session_id in the URL, which caused a 400 Bad Request error when trying to regenerate a section for an existing proposal, as the session might have expired.

This commit changes the endpoint to use proposal_id in the URL, which is a persistent identifier for the proposal. The endpoint now creates a temporary Redis session for the regeneration process, making the endpoint stateless and more robust. The corresponding test has been updated to reflect this change.

  • 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