Skip to content

Fix(knowledge): Use correct status enum and add logging

Edouard Legoupil requested to merge fix/knowledge-card-fallback into main_dev

Created by: Edouard-Legoupil

This commit fixes two issues:

  1. A DatabaseError caused by using an invalid value for the proposal_status enum. The status 'completed' has been replaced with the correct value, 'approved'.
  2. To help diagnose a potential re-ingestion issue, a log message has been added to the ingest_reference_content function to print the scraped_at timestamp.
  • 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