Skip to content

fix(backend): Make template loading more robust

Edouard Legoupil requested to merge feat/save-knowledge-content into main_dev

Created by: Edouard-Legoupil

The template discovery process in backend/core/config.py was not resilient to errors. If a single template file was malformed (e.g., japan_proposal_template.json), it would raise an exception and halt the entire loading process. This prevented any subsequent templates, including the valid knowledge card templates, from being registered.

This commit fixes the issue by modifying the get_available_templates function to continue processing other files even if one fails to load or parse. It now wraps the file processing in a try...except block that logs the error and continues to the next file.

Additionally, the logic is simplified to always map a template by its filename for direct access, which is needed by the knowledge card page.

  • 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