Skip to content

feat: Ensure knowledge file exists on card association

Edouard Legoupil requested to merge feature/ensure-knowledge-file-exists into main_dev

Created by: Edouard-Legoupil

When a knowledge card is associated with a proposal, this change ensures that the corresponding knowledge file exists in backend/knowledge.

If the file is missing, it is now automatically created by fetching the card's generated_sections from the database and saving them to a JSON file. This prevents errors during the proposal generation process when a knowledge file is expected but not found.

  • 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