Skip to content

fix: Correct duplicate knowledge card detection and modal flow

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

Created by: Edouard-Legoupil

This commit addresses two issues:

  1. The duplicate knowledge card detection on the dashboard was not working correctly. The logic has been rewritten to be more robust.
  2. The confirmation modal for creating a duplicate knowledge card was not appearing at the correct time. The logic has been moved to a useEffect hook that triggers on selection of a linked entity.

These changes ensure that duplicate knowledge cards are correctly identified and that the user is warned at the appropriate time.

  • 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