Skip to content

Fix: Handle multiple outcome IDs in knowledge card fetching

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

Created by: Edouard-Legoupil

This commit fixes a bug where the "Manage Knowledge" modal would only display one knowledge card even when multiple outcomes were associated with a proposal.

The root cause was that the backend endpoint /api/knowledge-cards was only processing a single outcome_id from the query string.

The following changes have been made:

  • The get_knowledge_cards function in backend/api/knowledge.py has been updated to accept a list of outcome_ids.

  • The SQL query has been modified to use an IN clause to fetch all knowledge cards that match any of the provided outcome_ids.

  • The frontend component AssociateKnowledgeModal.jsx was previously updated to correctly send multiple outcome_id parameters in the request.

  • 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