Skip to content

feat: Save generated knowledge card content to file

Edouard Legoupil requested to merge feature-populate-db-from-excel into main_dev

Created by: Edouard-Legoupil

Updates the backend/scripts/generate_card_content.py script to include the _save_knowledge_card_content_to_file functionality from the API.

This ensures that when knowledge card content is generated via the script, it is also saved to a corresponding JSON file in the backend/knowledge directory, mirroring the behavior of the API.

  • Copied the _save_knowledge_card_content_to_file function from backend/api/knowledge.py to backend/scripts/generate_card_content.py.

  • Adapted the function to use a psycopg2 cursor instead of a SQLAlchemy connection object.

  • Added a call to this function after new content is successfully generated for a knowledge card.

  • 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