Skip to content

refactor: Update all proposal templates to the new format

Edouard Legoupil requested to merge fix-update-all-proposal-templates into main_dev

Created by: Edouard-Legoupil

This commit updates all proposal templates to use the new, streamlined format for defining tables. It also fixes a bug in the content generation handlers.

Key changes include:

  • Updated All Templates: All proposal templates (proposal_template_cef.json, proposal_template_echo.json, proposal_template_japan.json, proposal_template_unhcr.json) have been reviewed and updated to ensure their table definitions conform to the new instructions-based format.

  • Bug Fix: The handle_number_format and handle_table_format functions in backend/utils/crew_actions.py have been fixed to correctly parse the JSON output from the AI and extract the generated_content.

  • Consistent Formatting: This ensures that all templates are now fully compatible with the refactored proposal generation and export system.

  • 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