Skip to content

feat: Add duplicate knowledge card detection and confirmation modal

Edouard Legoupil requested to merge feat-duplicate-knowledge-cards into main_dev

Created by: Edouard-Legoupil

This change introduces two features to prevent the creation of duplicate knowledge cards.

On the knowledge card creation screen, a confirmation modal now appears if a user selects a donor, outcome, or field context that already has an associated knowledge card. This warns the user of a potential duplicate while still allowing them to proceed if they intend to create an ad-hoc card.

On the dashboard, existing duplicate knowledge cards are now flagged with a "Duplicate" badge and a delete button, allowing for easier cleanup of redundant entries.

This is achieved by:

  • Modifying the /knowledge-cards endpoint to include the donor_id, outcome_id, and field_context_id in the response.

  • Updating the frontend to use these IDs to detect duplicates on both the dashboard and the knowledge card creation screen.

  • 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