Skip to content

Fix: Correctly fetch and display associated knowledge cards

Edouard Legoupil requested to merge fix-display-associated-knowledge-cards into main_dev

Created by: Edouard-Legoupil

This commit resolves a bug that caused the application to crash when loading a proposal draft. The issue was traced to an incorrect column name (title instead of summary) in the SQL query that fetches associated knowledge cards.

The following changes have been made:

  • The SQL query in backend/api/proposals.py has been corrected to use the summary column from the knowledge_cards table and alias it as title to match the frontend's expectation.

  • The load_draft endpoint now correctly returns all knowledge cards associated with a proposal.

  • The frontend component Chat.jsx has been updated to correctly consume and display these cards when a draft is loaded.

  • 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