Skip to content

Feat: Improve Knowledge Card UX and section ordering

Edouard Legoupil requested to merge feat/knowledge-card-updates into main_dev

Created by: Edouard-Legoupil

This commit includes two main improvements to the Knowledge Card feature:

  1. Fix auto-refresh after reference actions: The knowledge card view was not automatically updating after identifying or ingesting references for a new card. This commit fixes the issue by using react-router's location state to pass a trigger to the component after navigation. A useEffect hook now detects this state, initiates the correct action, and ensures the UI is updated with the new data. The relevant handler functions have been wrapped in useCallback for stability.

  2. Ensure correct section ordering: The generated content sections are now displayed in the order defined in the JSON template file. The rendering logic was updated to iterate over the proposal_template.sections array instead of the generatedSections object keys.

  • 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